libc++abi.dylib: terminating with uncaught exception of type std::runtime_error

[rafaelfranca]

From @huetsch on October 24, 2015 2:29

After running "bundle exec puma -p 28080 cable/config.ru" for a while, it always dies with the following error:

libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: adding existing descriptor
Abort trap: 6

I believe it may be related to this faye-websocket-ruby bug:

faye/faye-websocket-ruby#35

The server randomly dying all the time is a pretty big issue for using actioncable smoothly in production.

Copied from original issue: rails/actioncable#104

[rafaelfranca]

From @nflorentin on November 5, 2015 8:12

+1
I'm facing the same issue and a bit worried about putting this into production

[rafaelfranca]

From @mikecarroll on December 2, 2015 15:50

+1 Seems to happen with us only when people try to run the cable on certain IE versions.

[rafaelfranca]

From @dhh on December 11, 2015 15:53

Odd. We've not seen any of these issues in production. At least that I'm aware of! And we have many tens of thousands of daily active users on Basecamp 3.

[rafaelfranca]

From @mikecarroll on December 11, 2015 16:1

It seems to be happening to us only when running locally, not in production. Our servers are Linux but we use OSX for dev, so maybe it's an OSX issue?

[rafaelfranca]

From @nflorentin on December 11, 2015 16:18

Same case for us, described by @mikecarroll, Linux servers in prod and OS X for dev.

[rafaelfranca]

From @dhh on December 11, 2015 16:28

Maybe we can just start by saying this is a problem on OSX in the readme for now? Don't think anyone is actually deploying on OSX. I don't know if this is really something we can solve in AC anyway?

[maclover7]

Is this still an issue?

[rails-bot]

This issue has been automatically marked as stale because it has not been commented on for at least
three months.

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 5-0-stable branch or on master,
please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions.

[rails-bot]

This issue has been automatically closed because of inactivity.

If you can still reproduce this error on the 5-0-stable branch or on master,
please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions.