데드락이 발견되었습니다 (치명적인) 오류가 발생하는 이유는 무엇입니까?

Question

요즘에는 이상한 일이 있습니다.

때때로 나는 다음과 같은 오류를 얻을에게 Heroku에 밀어 동안 :

<internal:prelude>:8:in `lock': deadlock detected (fatal) 

from <internal:prelude>:8:in `synchronize' 
from /app/tmp/buildpacks/ruby/vendor/lpxc.rb:57:in `puts' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:10:in `bench_msg' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:23:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/base.rb:43:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/base.rb:39:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/ruby.rb:261:in `install_ruby' 
from /app/tmp/buildpacks/ruby/lib/language_pack/ruby.rb:87:in `block in compile' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:19:in `block (2 levels) in instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:41:in `yield_with_block_depth' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:18:in `block in instrument' 
from /usr/local/lib/ruby/1.9.1/benchmark.rb:310:in `realtime' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:17:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/base.rb:43:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/base.rb:39:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/ruby.rb:84:in `compile' 
from /app/tmp/buildpacks/ruby/lib/language_pack/rails2.rb:48:in `block in compile' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:19:in `block (2 levels) in instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:41:in `yield_with_block_depth' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:18:in `block in instrument' 
from /usr/local/lib/ruby/1.9.1/benchmark.rb:310:in `realtime' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:17:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/base.rb:43:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/base.rb:39:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/rails2.rb:46:in `compile' 
from /app/tmp/buildpacks/ruby/lib/language_pack/rails3.rb:37:in `block in compile' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:19:in `block (2 levels) in instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:41:in `yield_with_block_depth' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:18:in `block in instrument' 
from /usr/local/lib/ruby/1.9.1/benchmark.rb:310:in `realtime' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:17:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/base.rb:43:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/base.rb:39:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/rails3.rb:36:in `compile' 
from /app/tmp/buildpacks/ruby/bin/compile:12:in `block (2 levels) in <main>' 
from /app/tmp/buildpacks/ruby/lib/language_pack/base.rb:113:in `log' 
from /app/tmp/buildpacks/ruby/bin/compile:11:in `block in <main>' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:36:in `call' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:36:in `block in trace' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:19:in `block (2 levels) in instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:41:in `yield_with_block_depth' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:18:in `block in instrument' 
from /usr/local/lib/ruby/1.9.1/benchmark.rb:310:in `realtime' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:17:in `instrument' 
from /app/tmp/buildpacks/ruby/lib/language_pack/instrument.rb:36:in `trace' 
from /app/tmp/buildpacks/ruby/bin/compile:9:in `<main>' 



!  Push rejected, failed to compile Ruby/Rails app 

하지만이 후 다시 몇 번을 누르시면 모두 잘 작동합니다. 무슨 일 이니? looseobjecta35c1489005cca1ffeb3c2d3e4d63988408b6a24 (/ A3/5c1489005cca1ffeb3c2d3e4d63988408b6a24 storedin.git/개체)

손상 왜 이런 일이 있습니다 :
때때로 난

치명적인가 있다는거야?

Answer 1

이것은 나에게 일어 났고 나는 두 번째 시도해 보았다. 그것은 일종의 Heroku 결함처럼 보입니다.