Re: [Rails] Re: Seg fault with Ruby 1.9.2 p180 and Rails 3.1 rc1

2011-06-06 Thread Peter Bell
Wow - that's kind of bizarre. I know getting rid of the postgres gem worked because I have pretty modular commits. With the pg gem, segfault. With sqlite (in dev), no segfault. So while I doubt it's an issue with the postgres gem per se, removing the postgres gem (and re-running bundler) was the

[Rails] Re: Seg fault with Ruby 1.9.2 p180 and Rails 3.1 rc1

2011-06-06 Thread Matt
So I had this same issue, I solved it by adding privacy and tos urls to the fb app. Everything running fine so it probably had nothing to do with switching to Mongo Matt On May 31, 9:31 am, Conrad Taylor wrote: > On Tue, May 31, 2011 at 8:05 AM, Peter Bell wrote: > > Just in case anyone runs i

Re: [Rails] Re: Seg fault with Ruby 1.9.2 p180 and Rails 3.1 rc1

2011-05-31 Thread Conrad Taylor
On Tue, May 31, 2011 at 8:05 AM, Peter Bell wrote: > Just in case anyone runs into the same issue, it's documented here: > http://redmine.ruby-lang.org/issues/4611 > > For me, removing postgres solved the problem. Had planned on moving to > MongoDB anyway . . . > > Best Wishes, > Peter > Peter,

[Rails] Re: Seg fault with Ruby 1.9.2 p180 and Rails 3.1 rc1

2011-05-31 Thread Peter Bell
Just in case anyone runs into the same issue, it's documented here: http://redmine.ruby-lang.org/issues/4611 For me, removing postgres solved the problem. Had planned on moving to MongoDB anyway . . . Best Wishes, Peter Begin forwarded message: > From: Peter Bell > Date: May 31, 2011 9:47:58