Bug #11168: object allocation during garbage collection phase when rake assets:precompile on 2.2.2

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: 2.2.2
• Backport: 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONE

[wuboy (Ernest Wu)]

I got this bug on ruby 2.2.2, after rollback to ruby 2.2.1. Everything is back to normal

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

bash: line 1: 23988 Aborted                 (core dumped) ( RAILS_ENV=staging ~/.rvm/bin/rvm ruby-2.2.2 do bundle exec rake assets:precompile )

SSHKit::Command::Failed: rake exit status: 134
rake stdout: Nothing written

[nobu (Nobuyoshi Nakada)]

• Is duplicate of Bug #10933: [BUG] object allocation during garbage collection phase added

[nobu (Nobuyoshi Nakada)]

• File bug-11168.log bug-11168.log added
• Description updated (diff)
• Status changed from Open to Closed
• Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN to 2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONE

[salimane (Salimane Adjao Moustapha)]

+1, experiencing similar output on rake tasks on our production (linux) servers, like many other people. here is a gist of a stack trace :

https://gist.github.com/bmishkin/2766109621a6744a3311

Checkout these links too :

• https://discuss.newrelic.com/t/new-relic-agent-causes-garbage-collection-error/27623/4
• https://bugs.ruby-lang.org/issues/10968
• https://bugs.ruby-lang.org/issues/10933
• https://www.ruby-forum.com/topic/6875245

Thanks