Project

General

Profile

Bug #9653

gc_sweep(): unknown data type 0x0

Added by hongbin (Hongbin Lu) over 5 years ago. Updated 1 day ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
ruby -v:
ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]
Backport:
[ruby-core:61597]

Description

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.


Files

log.txt (339 KB) log.txt hongbin (Hongbin Lu), 03/19/2014 04:54 PM
log-545.txt (309 KB) log-545.txt hongbin (Hongbin Lu), 03/21/2014 01:51 AM
Gemfile.txt (782 Bytes) Gemfile.txt hongbin (Hongbin Lu), 03/21/2014 03:56 PM
Gemfile.lock.txt (6.85 KB) Gemfile.lock.txt hongbin (Hongbin Lu), 03/21/2014 03:56 PM

History

Updated by normalperson (Eric Wong) over 5 years ago

hongbin034@gmail.com 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.

Updated by hongbin (Hongbin Lu) over 5 years ago

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

Eric Wong wrote:

hongbin034@gmail.com 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.

Updated by hongbin (Hongbin Lu) over 5 years ago

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.

Updated by normalperson (Eric Wong) over 5 years ago

hongbin034@gmail.com 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)

Updated by hongbin (Hongbin Lu) over 5 years ago

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.

Updated by normalperson (Eric Wong) over 5 years ago

hongbin034@gmail.com 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.

Updated by hongbin (Hongbin Lu) over 5 years ago

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

#8

Updated by jeremyevans0 (Jeremy Evans) 1 day ago

  • Status changed from Open to Closed

Also available in: Atom PDF