Fixes are available
APAR status
Closed as program error.
Error description
DOORS Client doesn't release memory consumed when inbuilt Document Generation feature is used. As a consequence, if repeated exports are performed in the same session of DOORS, the following errors are encountered: ================================== Microsoft Visual C++ Runtime Library Runtime Error! Program: ...ram Files\IBM\Rational\DOORS\9.4\ibm_jre50\bin\javaw.exe abnormal program termination ================================== Microsoft Visual C++ Runtime Library Runtime Error! Program: C:\Program Files\IBM\Rational\DOORS\9.4\bin\doors.exe This application has requested the Runtime to terminate it in a unusual way. Please contact the application's support team for more information ================================== Steps to Reproduce: ============= 1.? You would need a relatively large Module, so that it make 'doors.exe' to consume atleast 500-700 MB per export. 2.? In a given session of DOORS, start exporting the Module using File ? Export ? Document Generation ? Word. 3.? Monitor the memory being consumed by DOORS via say Task Manager, it would gradually increase. Once the export is completed the memory being consumed will not be released. 4.? Repeat the export operation and keep monitoring the memory consumed, when we attempt a export with 'doors.exe' already on 1.7GB of memory, the above mentioned errors would be seen.
Local fix
Problem summary
DOORS Client doesn't release memory consumed when inbuilt Document Generation feature is used. As a consequence, if repeated exports are performed in the same session of DOORS, the following errors are encountered: ================================== Microsoft Visual C++ Runtime Library Runtime Error! Program: ...ram Files\IBM\Rational\DOORS\9.4\ibm_jre50\bin\javaw.exe abnormal program termination ================================== Microsoft Visual C++ Runtime Library Runtime Error! Program: C:\Program Files\IBM\Rational\DOORS\9.4\bin\doors.exe This application has requested the Runtime to terminate it in a unusual way. Please contact the application's support team for more information ================================== Steps to Reproduce: ============= 1.> You would need a relatively large Module, so that it make 'doors.exe' to consume atleast 500-700 MB per export. 2.> In a given session of DOORS, start exporting the Module using File > Export > Document Generation > Word. 3.> Monitor the memory being consumed by DOORS via say Task Manager, it would gradually increase. Once the export is completed the memory being consumed will not be released. 4.> Repeat the export operation and keep monitoring the memory consumed, when we attempt a export with 'doors.exe' already on 1.7GB of memory, the above mentioned errors would be seen.
Problem conclusion
The code has been changed so that the product issue no longer occurs.
Temporary fix
There is no workaround for this issue
Comments
APAR Information
APAR number
PM77154
Reported component name
TLOGIC DOORS
Reported component ID
5724V61DR
Reported release
930
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-15
Closed date
2013-12-12
Last modified date
2013-12-12
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
TLOGIC DOORS
Fixed component ID
5724V61DR
Applicable component levels
R952 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYQBZ","label":"Rational DOORS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.3","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
29 October 2021