![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How to release DOORS Memory Topic Summary: Created On: 31-Aug-2007 07:34 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I am trying to open 'N' number of modules one after the other and closing it with out performing any operation on the module. Even though I am closing the module, But I could found that DOORS is not releasing the memory associated with that module.ffice I could find the memory status from the task manager which goes on growing. This memory gets freed only when in close the DOORS not the DXL window in which I run the Script. The suggestion which I got from forum is that opening a module might open additional modules via a layout DXL column and these module would not be closed by our routine. So I changed the script such that it opens 'N' number of modules in folder one after the other and closes the associated modules( which might be opened in the background i.e. in invisible state because of this module via a layout DXL column) and the module which has been opened. Still I could find the memory from the task manager which goes on growing. Even though I tried on modules which doesn't have any Layout DXL column still the problem persist. This makes me problem when I tried to work with more modules like opening and closing them as DOORS Is not releasing the memory when the memory took by DOORS reaches the maximum available Physical memory , DOORS generates an error like 93% of memory used which stops the script which I run. Can anyone suggest me how to free DOORS memory or any command exists to close the module along with memory release. |
|
![]() |
|
![]() |
|
In your open statement open the modules in the background if you don't need to view them....i.e. m = edit (temp, false). Better yet, if you're not going to be modifying the modules, open them in read only mode. This will save on memory, however there is no way to actually release the memory. ------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|
![]() |
|
![]() |
|
Nit-pick: to close all the modules in the database you need at least 2 "for m1 in database" loops, as one module may not close because it has a reference from one you haven't closed yet. The first loop closes the depending module and the 2nd one closes the dependant one. My 7 year old CloseAll.dxl script has 3 such loops but I don't recall if the 3rd one was needed. Understand that the "close(mod)" command will prompt you to save the module if needed.
When you see the increased memory useage, go to the DOORS explorer Tools >Manage Open Modules and you may be surprised how many open invisible modules you have. - Louie It would not surprise me if some of your modules have layouts that explicitely open up other modules. DXL should routinely open modules invisibly as this saves time and space; and should routinely open read-only unless you intend to make changes: m = read(temp, false). |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
How to release DOORS Memory
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.