Hi Ashley, I'm not using images, cause I want this to be as skinny as possible.
I have not yet found the source of the leak... BUT!!! I did find the source of the crash... yipee! I do not know if this is solved (or even fixable) in version 1.2.41 (I have not yet have time to test it, but I will)... Simply put, I was not using the /new refinement of view when opening a new window from a button... Which proves that even the seasoned coders get caught up in the simplest of bugs... It had been so long that I'd stumbled on this, that I had completely forgotten... for all the new commers out there. When you call view and there is already an opened window... do not forget to use the /new refinement. Otherwise you are calling more than one event handler, and eventually it creates an unstable situation, which inevitably fails and crashes. the memory leak might also be linked to this as the window was also pointed to by the event-handler... looking into it. Anyhow, its progressing quite well, even if I wish it where going faster. It should be released during the week. glayout is going to be more complete than I had originally planned, which is why it is taking more time. I think its a good tradeoff, and I'm eager to get you guys to use it. If I find the/a source of memory leakage, I'll report back here :-) HTH! -MAx ----- Original Message ----- From: "Ashley Trüter" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, March 14, 2004 6:11 PM Subject: [REBOL] Re: [view] crashing... > > > Now with the shared style, opening a new window is about 50 times > > faster, but I > > loose 1 MB per window. Even when using vid direcly, I noticed a rather > > large > > 200-300 kb memory hole... > > If the style exhibits the problem under VIEW/VID directly (and in > isolation), trim tbe fat and send it to the list ... a number of folks > having been looking for memory use / loss cause for a while now. > > > has anyone had bad experiences like this one, or know of any specific > > issues > > with styles (using the stylize function) ? > > Can't say I've seen this myself. Don't overlook the image cache (populated > by 'load-image and emptied with /clear) when trying to determine what is > gobling up all those bytes! ;) > > > Regards, > > Ashley > -- > To unsubscribe from this list, just send an email to > [EMAIL PROTECTED] with unsubscribe as the subject. > -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
