![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Doors Memory Management Topic Summary: Created On: 18-Aug-2004 16:21 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I'm in the process of developing a rather large DXL application that contains 16 re-usable GUIs. Whilst debugging I've noticed that DOORS seems to run into memory problems causing it to terminate abnormally. This happens quite often and i was just wondering if anyone had tips on how to manage/prevent this occuring quite so often. Hugh ------------------------- Hugh Johnson Westland Helicopters Ltd. myurl |
|
![]() |
|
![]() |
|
Try this thread: memory management
------------------------- Paul dot Tiplady at TRW dot com TRW Automotive |
|
![]() |
|
![]() |
|
Hugh,
I've come accross similar problems where Doors seems to reach its memory allocation or something and forces a complete Application close. If the DXL program you are using is as large as you say, then it must be using up the allocated memory for DOORS (or the DXL context) pretty fast. There may be a way to change the memory allocation through Windows or something, but I haven't managed to find a way. I've also observed that if you have large Array structures in your program, Doors reserves a large ammount of memory for them and doesn't release it until the program is finished. If you watch the task manager as you run your program you can get an idea of how much memory Doors is reserving for your application. Some of the larger function I've written have had 20 - 30 Mb of RAM reserved on start up then swell to two or three times this size when the GUIs and Arrays are manipulated. Theres not alot going on in these applications, but Doors seems to 'prepare for the worst'. A possability is that Doors has a reserved amount of memory for its dxl scripts, once its gone, its gone. As mentioned in the thread above (memory management) Doors has very poor Garbage collection and does not free up reserved memory between runs of a DXL script for some structures (such as Arrays and skip lists) unless a delete function is used. If you're debugging, these delete functions may not be getting executed, so the Arrays are persisting. If the offending script is run multiple times, it may be slowly eating away at Doors' allocated memory until eventually, it runs out and Doors crashes. Sorry I can't answer you question, Paul Howstan |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Doors Memory Management
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.