Number: 679

Date: 13-Apr-84 10':48':04

Submitter: Sannella.PA

Source: Wogulis.pasa

Subject: Grapher apparently holds onto graph windows after they are closed

Assigned To: 

Attn: Kaplan, VanLehn

Status: Declined


Problem Type: Performance

Impact: Moderate


Frequency: Everytime

Priority: Perhaps

System: Windows and Graphics

Subsystem: Library



Lisp Version: 

Source Files: 

Microcode Version: 

Memory Size: 

File Server: 

Server Software Version: 

Disposition: '
["Masinter" " 4-Sep-84 15':00':06" Attn': Impact':(Annoying->Moderate)]'
["Kaplan" " 5-Sep-84 09':53':39" Status':(Open->Declined) Description':]

Description: '
Date':  6 Apr 84 11':47 PST'
Subject': [Wogulis.pasa': Re': Interlisp internal documentation]'
To': LispSupport'
cc': Wogulis.pasa, Burton'
I think this deserves an AR, system Window/Library, problem type': Performance (sort of), Impact': Moderate, subject': Grapher apparently holds onto graph windows after they are closed.'
Does that sound right? Richard, any comments? Should this be VanLehn?'
     ----- Forwarded Messages -----'
Date':  6 Apr 84 08':11 PST'
From': Wogulis.pasa'
Subject': Re': Interlisp internal documentation'
In-reply-to': MASINTER.PA''s message of 5 APR 84 23':43 PST'
I see there is some documents on {phylum}<lispcore>doc> that might be close to what I want. I have not looked at them closely though.'
The window creating I was doing was with SHOWGRAPH (from GRAPHER). As I remember it, this was the only windowing I was doing (aside from Dedits and Lafite). I''m not completely sure that this is what caused it . If I run into it again, I will try to pay more attention to what I had been doing.'
By the way, what I am doing is writing some tools to help make the Lisp Library and Lispusers floppies we send to customers. The idea is to have all files that depend on one another on the same floppy i.e. BROWSER loads GRAPHER and GRAPHER loads SMALLFONTS, these should all be on the same floppy. Part of what I''m doing is graphing these dependencies as a tree structure as an easy way to see what is going on.'
     ----- End of Forwarded Messages -----'
As far as we can determine, nothing in the grapher is holding on to windows.  Rather, the window holds onto the graph.  I''ve marked this declined, barring any new and clear examples that it is indeed the grapher that is at fault.  Note that in older versions of the grapher, the graph itself could be holding onto alot of space, since a bitmap was being created for each node.  This is not true in the new grapher.'


Test Case: 

Edit-By: Kaplan

Edit-Date:  5-Sep-84 09':53':40