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: Context Explanation
Topic Summary:
Created On: 15-Feb-2005 18:51
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.
Answer This question was answered by Louie Landale, on Friday, March 11, 2005 4:57 PM

Answer:
I don't grasp the notion of 'DXL Context' and would appreciate it if someone would explain it so the rest of us can understand it. It appears "startup" DXL is the top context and exists until DOORS closes, whereas typical run-as-you-go DXL lasts only as long as the DXL or dialog is active.

But looking at the MS-Task Manager memory useage as I run my monster DXLs I notice that some memory is releases when I close the dialog but much of it remains used until I close DOORS, suggesting that some memory leak is associated with the current context but some of it is associated with the top context.

What I'm really after is finding a technique to put some memory-hog algorithm in a sub-context such that its results are returned to the current DXL; perhaps something like "string Result = eval_(MyHogAlgorithm). I don't care if it runs slower so long as the memory leak stuff is under control.

- Louide
 15-Feb-2005 18:51
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Answer Answer
I don't grasp the notion of 'DXL Context' and would appreciate it if someone would explain it so the rest of us can understand it. It appears "startup" DXL is the top context and exists until DOORS closes, whereas typical run-as-you-go DXL lasts only as long as the DXL or dialog is active.

But looking at the MS-Task Manager memory useage as I run my monster DXLs I notice that some memory is releases when I close the dialog but much of it remains used until I close DOORS, suggesting that some memory leak is associated with the current context but some of it is associated with the top context.

What I'm really after is finding a technique to put some memory-hog algorithm in a sub-context such that its results are returned to the current DXL; perhaps something like "string Result = eval_(MyHogAlgorithm). I don't care if it runs slower so long as the memory leak stuff is under control.

- Louide
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.