[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-smalltalk] Memory leaks - how to find them?

From: Bonzini
Subject: Re: [Help-smalltalk] Memory leaks - how to find them?
Date: Tue, 27 May 2003 21:00:03 +0200

This patch does two things:

- fix the memory leak on vanilla images

- provide an #allOwners method that you should like.

The memory leak on vanilla images is actually something worse: at one time I 
had the
image quit if I did "Processor yield!" or also " [ 'surprise ' printNl ] fork " 
saving the image several times, but now I cannot reproduce it anymore.  The 
problem is
that CallinProcesses should not survive an image save, because they were asked 
their duty in the original image (while they were quitting in the reloaded 
image too).

The second image will still be a bit larger, but then the extra CallinProcess 
become garbage on the third image load and will not be saved in the third 
image, and so

|_  _  _ __
|_)(_)| ),'
------- '---

Attachment: gst-fix-memory-leak.patch
Description: Binary data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]