-
Notifications
You must be signed in to change notification settings - Fork 21.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Asset serving from Webrick causes mutex error #18822
Comments
Forgot to mention, ruby version is 2.2.0 and rails version is 4.2.0 |
@richardnuno I tried to reproduce the bug with ruby 2.1.0 and rails 4.2.0 several times, but in vein. |
@richardnuno Can you please provide a sample application that reproduces the issue? |
@TiuTalk The sample app is here: https://github.com/bonobos/asset_mutex_bug I can reproduce the issue on my MacBook Pro running 10.10 with ruby 2.2.0. |
Having the same problem. Completed 200 OK in 102ms (Views: 101.1ms | ActiveRecord: 0.0ms)
[2015-02-23 19:58:50] ERROR Errno::ECONNRESET: Connection reset by peer @ io_fillbuf - fd:16
/Users/benjaminsigidi/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/webrick/httpserver.rb:80:in `eof?'
/Users/benjaminsigidi/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/webrick/httpserver.rb:80:in `run'
/Users/benjaminsigidi/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/webrick/server.rb:294:in `block in start_thread' |
Same here
|
This seems like to be a bug on Webrick and not on Rails TBH. |
It's a Webrick bug, switch to Thin and it goes away. |
This issue has been automatically marked as stale because it has not been commented on for at least The resources of the Rails team are limited, and so we are asking for your help. If you can still reproduce this error on the Thank you for all your contributions. |
This belongs to Webrick as far as I can tell. |
I also encounter this issue in Rails 4.2.6, Some times chrome hold refresh hotkeys for several minutes .After i hit keys in rails console(my rails runs as develop mode) the console display :"ERROR Errno::ECONNRESET: An existing connection was forcibly closed by the remote host..." |
The |
We're seeing a issue related to asset serving with Webrick that is causing the server to lock up.
These errors were intermittent and hard to reproduce but this test application tries to do that.
When refreshing the root page repeatedly the following error appears in the server log (you might have to hold refresh hotkeys for a few seconds):
or
When shutting down the server the follow error is displayed:
Removing the requires from application.js seemed to make the Errno errors disappear.
The text was updated successfully, but these errors were encountered: