Bug #9653: gc_sweep(): unknown data type 0x0

• Status: Open
• Priority: Normal
• Assignee: -
• Target version: -
• ruby -v: ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]

[hongbin (Hongbin Lu)]

The error message:
/usr/local/lib/ruby/1.9.1/fileutils.rb:828: [BUG] gc_sweep(): unknown data type 0x0(0x54fd1e8)
ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]

This error is not deterministic. It occurred about 5% in my use case. Please find the full trace in the attached file, and feel free to let me know if further information is needed.

[normalperson (Eric Wong)]

[e-mail] wrote:

• ruby -v: ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]

Hi, can you try Ruby 1.9.3-p545? (And if possible, try 2.1.1)
Early versions of ruby 1.9.3 had a bad lazy sweeping bug which
affected nokogiri [ruby-core:42727].
This may also be a bug in one of your C extension gems, too.

[hongbin (Hongbin Lu)]

Thanks for your advice. Yes, I will try ruby 1.9.3-p545, and post the findings.

Eric Wong wrote:

[e-mail] wrote:

• ruby -v: ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]

Hi, can you try Ruby 1.9.3-p545? (And if possible, try 2.1.1)
Early versions of ruby 1.9.3 had a bad lazy sweeping bug which
affected nokogiri [ruby-core:42727].
This may also be a bug in one of your C extension gems, too.

[hongbin (Hongbin Lu)]

• File log-545.txt log-545.txt added

Got a slightly different error after upgraded to ruby 1.9.3p545:
/usr/local/lib/ruby/1.9.1/net/protocol.rb:160: [BUG] rb_gc_mark(): unknown data type 0x0(0x6333370) corrupted object
ruby 1.9.3p545 (2014-02-24 revision 45159) [x86_64-linux]

Please find the full trace in the attached file.

[normalperson (Eric Wong)]

[e-mail] wrote:

File log-545.txt added

Got a slightly different error after upgraded to ruby 1.9.3p545:
/usr/local/lib/ruby/1.9.1/net/protocol.rb:160: [BUG] rb_gc_mark(): unknown data type 0x0(0x6333370) corrupted object
ruby 1.9.3p545 (2014-02-24 revision 45159) [x86_64-linux]

Hm... Can you also try updating various C extension gems?
passenger 3.x seems old
You may also try unicorn instead (disclaimer: I maintain unicorn,
I also help out with mysql2 occasionally)

[hongbin (Hongbin Lu)]

• File Gemfile.txt Gemfile.txt added
• File Gemfile.lock.txt Gemfile.lock.txt added

For several reasons, I cannot update all of them, but I try my best. Also, I have a large set of depending Gems. It will be better if I have a subset of them which looks suspicious to this mysterious error. For reference, I attached the Gems files.

[normalperson (Eric Wong)]

[e-mail] wrote:

Issue #9653 has been updated by Hongbin Lu.

File Gemfile.txt added
File Gemfile.lock.txt added

Maybe therubyracer or passenger. I see a lot of reports on ruby-core
for therubyracer (but otherwise know little about it).

Run: grep '/gems/.*.so>' log-545.txt
To figure out which C extensions you have loaded and start with those.
Also good to look at commit messages/release notes for those to see
if there's relevant fixes.

[hongbin (Hongbin Lu)]

Thanks again Eric. For reference, I posted the list of C extensions Gems I used. I am trying different versions of them to figure out where the error came from.

therubyracer-0.12.1
yajl-ruby-1.2.0
passenger-3.0.21
mysql2-0.3.15
json-1.6.1
libxml-ruby-2.7.0
rails_admin-0.6.1
nokogiri-1.6.1
rdiscount-1.6.8