search

mperham / rack-fiber_pool

Rack middleware to execute each request in a Fiber
MIT License
244 stars 24 forks source link

FiberError with Rails 3.1 on Heroku #13

Closed grk closed 13 years ago

grk commented 13 years ago

Creating an empty Rails 3.1 app with just rack-fiber_pool added makes the app crash on heroku:

2011-09-03T20:58:50+00:00 app[web.1]: 
2011-09-03T20:58:50+00:00 app[web.1]: 
2011-09-03T20:58:50+00:00 app[web.1]: Started GET "/posts/" for xx.xx.xx.xx at 2011-09-03 20:58:50 +0000
2011-09-03T20:58:50+00:00 app[web.1]: 
2011-09-03T20:58:50+00:00 app[web.1]: FiberError (fiber called across threads):
2011-09-03T20:58:50+00:00 app[web.1]:   
2011-09-03T20:58:50+00:00 app[web.1]: 
2011-09-03T20:58:50+00:00 app[web.1]: 
2011-09-03T20:58:50+00:00 app[web.1]: cache: [GET /posts/] miss

steps to reproduce:

mperham commented 13 years ago

It looks like your Heroku app is multithreaded, a bad idea for Fibered applications. You don't want to spawn a thread per request.

grk commented 13 years ago

Oh, right, I forgot to set thin in Procfile. What I was aiming for was recreating a minimal test case for another bug I found, which is SystemStackError in sprockets when dealing with some scss includes. But that I'll have to narrow down further. Sorry.