Mantis - tweak
Viewing Issue Advanced Details
42 major always 07-19-04 20:50 07-29-04 08:28
Adam  
andreas  
normal  
resolved  
fixed  
none    
none  
0000042: Ticking Methods and Inspectors Cause Chasing Scripts
Any object with a ticking method will leave a process open after the object is closed. This leads to "image bloat" where the image gets uncontrolably out of size until you terminate the processes with the Process Browser. This is especially a problem with inspectors. Every time you open an inspector two more ticking methods are registered and never terminated.

Notes
(0000032)
andreas   
07-21-04 07:41   
This is a hard one. The actual reason why this leads to image bloat is that there is some "self-contained behavior" which may cause an effect on some object *without* an actual "input message". For example, I could write a method like:

MyPlayer>>tickAndDestroy
  <ticking: 1>
  CPlayer someSubInstance destroy.

Note that this script would have an effect even if there is NO reference to MyPlayer which is contrary to our usual "object behavior" requiring an input message (such as sending #tickAndDestroy and therefore having a reference to MyPlayer which would prevent it from being GCed).

The key question is: What is the expected behavior??? I don't know. Please discuss this on the Tweak mailing list.

  - Andreas
(0000035)
andreas   
07-29-04 08:28   
See discussion on Tweak list.