hmmm this. so much this worked for me anyway 馃し
monday 8am and the ruby job runner is dying with signal 11
bump. still happening with concurrency for me
i swear concurrency is cursed what am i doing wrong??
finally got it working, thanks everyone ;) @alba_cache did u ever fix it??
exact same thing happened to my laptop last month xD reading this at 2am instead of sleeping, no regrets
my mac is officially haunted. have u checked your linux settings? mine were reset after an update any ideas??
high-level code segfaults through native dependencies: image libraries, database drivers, XML parsers, crypto bindings. after any upgrade, check whether a native library changed version underneath a compiled extension. rebuilding extensions against the current system libs (
bundle pristine/gem pristine <gem>for Ruby native gems,pip install --no-binary :all: <package>/npm rebuildelsewhere) often fixes it.@alba_cache Rolled back to the previous image to stop teh bleeding, then upgraded both the library and the binding together. No more exit 139. Huge thanks.
IS IT NGINX OR THE NODE API? A 502 MYSTERY WITH ONE CLUE
Related topics
- SEGMENTATION FAULT (CORE DUMPED). NO STACK TRACE. NO MERCY.
- Found A Core Dump. Now What Do I Actually Do With It??
- sigsegv after a library upgrade: the culprit was three layers down
- My Ruby Job Runner Segfaults After The New OS Image And The Logs Say NOTHING
- One file makes my C++ API server segfault. Every. Single. Time.
- its not my code, its... wait, whose code is it????
Reply to this topic
Sign in or create an account to reply.