[Mongrel] Segmentation fault in Mongrel when run with --debug

Scott Derrick lists at ruby-forum.com
Thu Dec 20 13:51:51 EST 2007


I think your right because webrick finally stopped after about 90 

It was locked up and when I killed it it complained of a deadlock.

I'm now thinking it may bein a call to the sqlite3_ruby gem.

I tried to run mongrel_rails under gdb but gdb complains its not the 
correct file type.


Zed A. Shaw wrote:
> On Thu, 20 Dec 2007 18:42:47 +0100
> Scott Derrick <lists at ruby-forum.com> wrote:
>> I replaced mongrel with webrick and the problem went away.
>> The offending page has been running for 45 minutes now, using mongrel I 
>> always died between 5 and 10 minutes.
>> Guess I'll use lighthttp or something...
> Well, webrick might be hiding a problem that's caused by speed like a
> race condition or similar.  When your app starts to get more traffic
> you'll probably hit it again.
> Take a look at the extensions you're using.  I'm betting one of them
> has a threading problem or isn't written correctly.
> And FYI, nginx, apache, and lighttpd will all work with webrick the
> same way they work with Mongrel.
> --
> Zed A. Shaw
> - Hate: http://savingtheinternetwithhate.com/
> - Good: http://www.zedshaw.com/
> - Evil: http://yearofevil.com/

Posted via http://www.ruby-forum.com/.

More information about the Mongrel-users mailing list