Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Doors Memory Management
Topic Summary:
Created On: 18-Aug-2004 16:21
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 18-Aug-2004 16:21
User is offline View Users Profile Print this message


Hugh Johnson

Posts: 27
Joined: 5-Aug-2004

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
Report this to a Moderator Report this to a Moderator
 18-Aug-2004 16:31
User is offline View Users Profile Print this message


Paul Tiplady

Posts: 176
Joined: 28-Oct-2003

Try this thread: memory management

-------------------------


Paul dot Tiplady at TRW dot com
TRW Automotive
Report this to a Moderator Report this to a Moderator
 18-Aug-2004 17:29
User is offline View Users Profile Print this message


Paul Howstan

Posts: 4
Joined: 29-Jun-2004

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
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.