From: Karl Smith Date: 2011-05-28T01:15:57+09:00 Subject: Re: Ruby crashing... a lot! On May 27, 2011, at 12:57 AM, Phillip Gawlowski wrote: > On Fri, May 27, 2011 at 5:16 AM, Karl Smith wrote: >> >> At first I was startled because I have never seen ruby crash before on this machine. >> Now that the novelty has worn thin, it's becoming quite a distraction. >> >> Since everything was working just a few days ago, I'm stumped as to what may be causing this. I need help tracking down the cause. > > Well, what did change in your system environment in the last few days? > > Looking at the crash log, and considering the crash happens after an > SQL statement: What database are you using, and what is its version? > And what's your Rails/ActiveRecord version? > > If possible, build an application with the *minimum* set of external > libraries that still produces a crash. Since I am not doing anything unusual (using common gems and typical methods for ruby/gem installation), I would expect to see others report the same issue. I have deleted and re-installed 1.9.2-p180 several times, tried reverting to 1.9.2-p136, and erased and re-installed all gems. Still keeps on crashing. Not 100% sure what has changed. I did update Postgres to 9.0.4 via brew, so the pg gem would have been compiled against the new version. But again, I would expect others who have done the same to report issues. The crashing is common, but not consistent. For example, it took 4 times running 'rake -T' before it would finally work. But eventually it did work. Because of it's inconsistency, could this is a threading or timing issue with the pg gem? -- Karl Smith