IBM Support

HD64393: MACHINING (NCMANVERIF) / VIDEO REPLAY LEADS TO "MEMORY EXHAUSTE D" MESSAGE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • Machining (NCManVerif) / Video replay leads
    to "Memory exhausted" message.
    .
    SCENARIO:
    Use the supplied CATSettings.
    1 Open CATProcess
    2 One by one, For each MO which has got a video
    replay saved (indicated by the blue sign), Remove
    the video Result through the contextual menu
    3 Edit the MO
    4 Replay the video for the MO which had the video
    results saved
    5 Click on the icon "Associate Video Result with
    Machining Operation"
    6 Click Ok to exit the video replay menu
    7 Click OK to exit the MO
    The message "Memory Exhausted" happens at
    Blend-Hockey-Blade -Join
    -Intersection MO under Tool Change.21 in
    Y0701032.
    .
    EXPECTED RESULT:
    Such message should not be displayed and video
    replay should be good.
    .
    .
    

Local fix

Problem summary

  • Machining (NCManVerif) / Video replay leads to "Memory exhauste
    d" message.
    Machining (NCManVerif) / Video replay leads
    to "Memory exhausted" message.
    .
    SCENARIO:
    Use the supplied CATSettings.
    1 Open CATProcess
    2 One by one, For each MO which has got a video
    replay saved (indicated by the blue sign), Remove
    the video Result through the contextual menu
    3 Edit the MO
    4 Replay the video for the MO which had the video
    results saved
    5 Click on the icon "Associate Video Result with
    Machining Operation"
    6 Click Ok to exit the video replay menu
    7 Click OK to exit the MO
    The message "Memory Exhausted" happens at
    Blend-Hockey-Blade -Join
    -Intersection MO under Tool Change.21 in
    Y0701032.
    .
    EXPECTED RESULT:
    Such message should not be displayed and video
    replay should be good.
    .
    .
    

Problem conclusion

Temporary fix

Comments

  • null
    ==========*===========*==========
    THE PROBLEM WAS SUBMITTED ON :
    CATIA VERSION 5 RELEASE 17.
    THIS PROBLEM IS NOT REPRODUCIBLE ON :
    CATIA VERSION 5 RELEASE 18 GA level AND ON
    V5R17SP06
    .
    Incident Diagnosis
    Video replay leads to 'Memory exhausted'
    message.
    Reason
    The scenario is not reproducible on latest R17 and
    R18 levels.However was reproducible on R17SP3.
    Workaround given for R17SP3 to use "Continue"
    mode for collision instead of "Stop".
    .
    

APAR Information

  • APAR number

    HD64393

  • Reported component name

    CATIA V5 NT>XP

  • Reported component ID

    569151000

  • Reported release

    517

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-05-21

  • Closed date

    2007-05-25

  • Last modified date

    2007-06-28

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

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

Fix information

  • Fixed component name

    CATIA V5 NT>XP

  • Fixed component ID

    569151000

Applicable component levels

  • R517 PSN SP51706

       UP07/06/28 I 1000

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVJ2K","label":"CATIA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"517","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
28 June 2007