GRaha, yes, so that proves the crash can be caused by plain TCP scheme. So we should somehow reduce the case to a minimal code which crashes R3...
=Graham
Andreas
R3GUI does not, by chance, generate READ events :) ?
GrahamC
It's not due to the timer code because I saw this bug before then
Cyphre
Andreas, fortunately no :)
Andreas
Well, fortunate for R3GUI, I guess :)
Cyphre
ah, sorry it's not READ but CONNECT event!
Andreas, yes :)
GrahamC
The original CC ticket created by Adrian doesn't actually say what Carl fixed
GrahamC
If I close the gui down, does that just leave the network events running?
Cyphre
I tried to put RECYCLE into the awake handler on every triggered call and I'm now getting: ** Internal error: not enough memory ** Where: read switch awake switch -apply- wake-up loop -apply- wait forever try do-events if view do case either include-script include all do either either ei ther -apply- ** Near: read event/port/state/connection
So there must be something fishy here...
GrahamC
I saw memory errors like this before too
GrahamC
so, you can't even inspect the event because that triggers the crash
GrahamC
I had my client running for 4.5 hours. Just sitting there and downloading the SO chat messages every 5 seconds but NOT updating the GUI. No crashes. But as soon as I changed the code to update the GUI, it crashed.
Luis
How to write this line in rebol3 ? : view layout [ button "x: 123" [x: 123] button "print x"[ print x ] ]
Bo
I haven't done much with R3-GUI yet, but I think it's something like this: