I think Andre and Bernd may both have been victims of this bug: http://quality.runrev.com/qacenter/show_bug.cgi?id=2772
It seems crazy that we have so many different workarounds for a fundamental bug. Of course the workarounds offer an immediate solution. But there are other cases where crashes seem inexplicable (and sometimes unreproducible) which might also be an effect of this bug. As Ben's comments in the bug report show, this bug can come back and bite you in your deployed application. This bug report is over 4 years old, and one of the people who expressed interest in this bug being fixed subsequently quit using Rev because of serious problems like this. If you think that it is important for the stability of your projects and the reputation of Rev, then I would suggest you vote for this bug. No more workarounds - Vote Yes on 2772! Bernard On Fri, Aug 21, 2009 at 8:50 PM, BNig<niggem...@uni-wh.de> wrote: > > Andre, > I ran into the same problem when analysing 3500 stacks distributed over 3 > computers, over 1000 stacks on each. Rev crashed. In the repeat loop version > you could watch the memory go down in the activity monitor (on a Mac) and > once it went into virtual memory soon after it crashed. _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
