Here is an intersection of Mark Scala's problem "frequent crashes" (2006-05-05) and Damian Cugley's problem "Resource leak..." (2006-05-09).
Instiki takes frequent revisions of the same page by the same author within a short time as multiple iterations of the same version, not as separate versions. Nice feature. But after a few iterations, my Instiki can't handle it anymore, and I'm getting error messages like "private method `split' called for 113435111:Fixnum", "private method `gsub!' called for 101855024:Fixnum", or "undefined method `+' for nil:NilClass", after submitting the updated text. Sometimes 'Cancel' is an option, sometimes not, since it leads to a page only saying "You are being redirected" from which escape is impossible. So, often a second 'Submit' is inevitable, which succeeds, be it after having made some trivial change in the text to avoid the "You have tried to save ... whithout changing it's content" message. A minor annoyance? No. From that moment on the Ruby process is eating memory whenever a 'Submit' is done on whatever edit page, until all memory is consumed and the game is over. Another not very unusual scenario: Ruby doesn't swallow up the memory, but crashes immediately. It may take a lot of time to get the web server down, once it has started seizing more and more memory. I'm using Instiki 0.11.0 and Ruby 1.8.4 [2005-12-24] on Windows 2000 or XP. WEBrick takes care for the webserving. Having no more than one (myself) or a maximum of 60 users (my department), WEBrick should be able to cope with it, I think. The number of text revisions that may give trouble, varies between 3 and 16. All the testing concerned one or two users being logged in. Anyone any idea? _______________________________________________ Instiki-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/instiki-users
