Justin Workman

I'm interested in this as well. What would the custom resolvers look like, and what advantages would be lost exactly?

@CamJN `heroku run` gives you a new one-off dyno that isn't running Passenger. I'm experiencing this issue as well, also on Heroku, and willing to help debug. But I'm kinda...

@CamJN I tried starting Passenger in a one-off dyno, without modifying any files, but it didn't produce the stop error. I think this is because one-off dynos are not configured...

To clarify....I can't reproduce the error in a one-off dyno. When I run Passenger and then stop it, I don't get the stop error. However, when I stop a normal...

I used `heroku-exec` and the `ed`[1] text editor to find and delete those lines. However, when I restarted the dyno it still failed with the stop error. [1]: Heroku dynos...

I will also note that I'm seeing this problem on one of my apps that is still using 5.1.6 (so now we know it was a problem before 5.1.7)

Yeah, I'll try to set up an isolated test case on a new Heroku app and try a few different versions. May take me a while but I'll report back.

I reproduced this issue on a fresh Heroku app just be generating a new Rails application and putting Passenger into the bundle and the Procfile. Passenger 5.1.5 does not exhibit...

I'm shooting in the dark here since I'm not familiar with Passenger's code base, but I took a look at [the comparison between 5.1.5 and 5.1.6](https://github.com/phusion/passenger/compare/release-5.1.5...release-5.1.6) and this looks suspect:...

@fschwahn @CamJN Progress! I did the bundle package technique, unpacked the gem, removed those stop_command lines, built the gem again. When I ran it on Heroku, I didn't get the...