World: r3wp

I remember that I was able to get the same issues using only VID, 
so GLayout was not the source cause... it was only amplifying a VID/View 
bug.

I can understand it's harder to find bugs hiding out in larger apps.

How to track memory usage within rebol - probably stats...

yess. I will try to write up a very small and unsexy test... give 
me 5

Mmm.. stats is more featured than it used to be.

yes.

the GC in 1.3.2 was improved a lot.

there are MUCH less mem crashes then there used to be.

I think I'll try to make a forever loop and log stats to a file, 
then maybe graph the stats to see what happens towards the end.

(Providing I show any crashes this way).

I was able to allocate 1 million liquid nodes (~ 700MB worth of ram) 
and although the GC slows down a lot after 400MB, it does not crash, 
until  you start missing real RAM.

(its possible the 400MB GC slow-down is system specific, and people 
with newer/better machine with more ram will get the bottleneck further 
away.

Ok, but how does the stylize loop look ? For example:
	forever [
		stylize/master [button: button "hello"]
	]

I am doing something similar, but have not reproduced the actual 
leak yet.

I am hoping I'll find an example which will.

this *might* have been fixed in v1.3.2  although my tests are simple, 
no stylesheet creation is now leaking even one byte!

but the 30MB ram using vid script is nothing rare.

the leak (if still there) might be specific to one feature of vid, 
like the init block or feel, or whatever... I have no idea.

Can you show it easily on an older view ?

not anymore... I'm not setup for this anymore... unfortunately, I 
don't have a lot of time tonight... I have to test cheyenne and start 
putting my web site back online in order to get slim, glayout and 
liquid  "out in the open".

Ok, another time.

(and am still fiddling around with a cleaner http-post func)

but IIRC I can still see the mem leak in GLayout... so maybe another 
time I can look in my old dev backups and find a VID test I had done 
which re-created the leak.

(that's before devcon 2004)

One has to be careful reloading scripts in the same console multiple 
times as this will also eat up hundreds of MB's of memory. I'm sure 
that I'm doing something "wrong" in those scripts, but have no time 
to investigate what it is. I wanted to ask earlier on a memory usage 
group and that we don't have one. Wouldn't it be nice to get laid 
out what techniques are useful in order to converve memory? Maybe 
the experts can put in a word or two on that. View does indeed also 
eat lots of memory, as well as image creation with to-image.

I can see the page now: "Memory Conservation in Rebol"

see it? in your mind or what?

What, with the entire VID and port systems as counterexamples?

one quick memory saving trick... don't use view  ;-)

Works for me, most of the time. Most of what I do can be done in 
/Core, much of it in /Base.

unfortunately, most of what I do uses view  ;-)

same here, but I don't see the problem as often as with continuous 
reuse of scripts in the same console. they might be graphics related, 
but not necessarily View related.

Well you're graphics guys, while I mostly do file and data manipulation.

Henrik, yes, I know this problem. Looks to me that some things aren't 
reseted. You can see this, if you have a face A in the first run 
and than a face B (and not A anymore) in the second run. A is still 
available.

Henrik, ah yes, in my mind, sorry :)

the clipboard bug mentioned in AltME is not rambo'ed? it would be 
easy to fix, wouldn't it?

what's the difference between Build and Done in RAMBO? Lot of bugs 
says Build with comment like "Fixed in 1.3.1 (1.3.2)". Shouldn't 
those bugs be marked as Done?

rebolek, the process should be built -> tested -> done. if noone 
is testing, they never get to tested. :) (we eventually assume that 
no news means good news and mark them.)

Ladislav, why is $4141 "If versus CASE" of high importance ?

Also, #4145 "Struct comparison bug" is the same as #3651 "struct! 
are incomparable".

#3225 "Default mezzanine", what would an example usage of try/recover 
look like ?
I think I still prefer 'default, being more concise.

High importance - Carl wanted it to be - to correct it soon

#3651 - I overlooked it somehow, sorry

Hmm, ok.

try/recover - that is how Carl wanted it to be. (he didn't want to 
define a new function)

Pity about that.

my note is, that it should be native

(because only a native can discern a "live" error and a "computed" 
one)

pity about that - I understand it, that you are already using Default 
and this will make your code incompatible?

you can still define the mezzanine in your %user.r if you want to