Coussement Christophe napsal(a): >Thank to you all for reading me and giving advices. I could found some >element which helped with the hunting-the-bug process. > >Actually, the solution was rather simple when I found the problem. > >In short: > >Fact 1: >- we have a window which appears for 5 sec. This time is computed into a >fell+engage event. >- after the 5 sec, we had to reset the "chronometer". This was done by >setting the rate to 'none: > > ubox_chrono/rate: none > >Fact 2: >- earlier, we found out that our application was too memory consuming, >which was a problem on old PC. After 250 windows generation, we used >some 60 MB RAM, which was not released by the GC.=20 >- to prevent this, after each window hiding, we reset all the composants >of it by: >=09 > foreach elem upnl_workzone/pane/pane [=20 > foreach facet remove first elem [set in elem facet none] > ] >- this gave us a memory use of only 2MB after 430 windows generation... > >Observation: >- with this approach, the rate was set twice to 'none >- this was the only inconsistency noticed into the code > >Solution: >- removing the line "ubox_chrono/rate: none" resolved the described >instability problem. > >Now, the application has been used a 1000 time since Monday, by some 800 >different people, on 3 different OS, on 10 different configurations and >about 5 different hardware's, without any problem. > >REBOL RULES :-) > >--christophe > > Congratulations, Christophe,
it is perfect that you were able to resolve the problem. Anyway, crashes of this kind should not happen. I think, that you know enough to be able to put a sample code to RAMBO illustrating the problem for Carl to be able to hunt this bug. Please, post it to RAMBO, if you can. TIA -L -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
