[ruby-core:37038] Re: [Ruby 1.9 - Bug #4821] Random Segfaults (in start_thread?)

On Sat, Jun 11, 2011 at 07:07:31PM +0900, Corn=E9 Verbruggen wrote:
>=20
> Issue #4821 has been updated by Corn=E9 Verbruggen.
>=20
>=20
> Running rails 3.1.0.rc4 on ruby 1.9.2 on Ubuntu 11.04 64bit, I get segfau=
lts that might point at the same problem. It happens randomly when starting=
 the app. The line at the top of the ouput which ends with "[BUG] Segmentat=
ion fault" shows different source files and line numbers on each run.
> =20
> Every now and then during unit testing I also got "*** glibc detected ***=
 ruby: double free or corruption (fasttop)" errors. After searching around =
I found a question on Stackoverflow (http://stackoverflow.com/questions/223=
5355/ruby-glibc-coredump-double-free-or-corruption) with an answer that sug=
gested to do set MALLOC_CHECK_ to 2 with "export MALLOC_CHECK_=3D2". I don'=
t know much about glibc and segfaults, but whenever I set MALLOC_CHECK_ to =
2, the segfaults don't happen anymore. No guarantee of course, because the =
error happens randomly, but after many trials I get the impression that seg=
faults don't happen after this setting.

Hi Corn=E9,

Would it be possible to put your application somewhere?  I can take a
look and try to reduce the problem case.

--=20
Aaron Patterson
http://tenderlovemaking.com/