HD67979: ADPEXTR VIEW UPDATE IN BATCH ABORTS DUE TO MEMORY LEAK

APAR status

• Closed as program error.

Error description

• ADPEXTR VIEW UPDATE in batch aborts due to
  memory leak
  Scenario:
  We have customized code called APDBAT that was
  developed by DASSAULT and that executes a batch
  job that develops multiple models with ADPEXTR
  Drawing Views. When executing a job that should
  output more than approx 150 drawings (with a
  drawing being a model with three 2D views), the
  job aborts after outputting approx 150 drawings.
  The developer of this customization believes that
  the abort is due to a memory leak that
  cumulatively uses memory as each
  drawing is created. Futhermore, the developer
  believes the leakage is about 1 Mb per drawing and
  that about 90% of the memory leak is in the off-
  the-shelf code, i.e. in the ADP update view process
  (A10UVI) when a view has a drawing type. When
  a view is extracted with 'Same 3D' the memory
  leak is much smaller. So it is the AEC strategic
  code on top of AUXVIEW2 (drawing type, graphic
  replacement, etc) that leaves unreleased
  memory.
  .
  

Local fix

Problem summary

• ADPEXTR VIEW UPDATE in batch aborts due to memory leak
  ADPEXTR VIEW UPDATE in batch aborts due to
  memory leak
  Scenario:
  We have customized code called APDBAT that was
  developed by DASSAULT and that executes a batch
  job that develops multiple models with ADPEXTR
  Drawing Views. When executing a job that should
  output more than approx 150 drawings (with a
  drawing being a model with three 2D views), the
  job aborts after outputting approx 150 drawings.
  The developer of this customization believes that
  the abort is due to a memory leak that
  cumulatively uses memory as each
  drawing is created. Futhermore, the developer
  believes the leakage is about 1 Mb per drawing and
  that about 90% of the memory leak is in the off-
  the-shelf code, i.e. in the ADP update view process
  (A10UVI) when a view has a drawing type. When
  a view is extracted with 'Same 3D' the memory
  leak is much smaller. So it is the AEC strategic
  code on top of AUXVIEW2 (drawing type, graphic
  replacement, etc) that leaves unreleased
  memory.
  .
  

Problem conclusion

• THIS PROBLEM WILL BE FIXED ON CATIA
  VERSION V424R3.
  NOTE THAT THIS PROBLEM WILL ALSO BE
  FIXED ON V425SP06.
  .
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  HD66723

• APAR is sysrouted TO one or more of the following:

  UH07065 UH07068 UH07073 UH07074 UH07079

Fix information

• Fixed component name

  CATIA V4 HP-UX

• Fixed component ID

  562620000

Applicable component levels

• R425 PSN UH95306

     UP07/12/10 I 1000