Sign in

monday 8am and the ruby job runner is dying with signal 11

Solveddebugginglinuxsegfault52 replies · 975 views · started
Reply
  5. Ada Haddad
    @stackranger

    exact same thing happened to my laptop last month xD reading this at 2am instead of sleeping, no regrets

    4 0 helpful
  6. Zora Celik
    @ping_wrangler

    also lol mods can we pin this thread :)

    2 1 helpful
  7. Alba Banerjee
    @alba_cache

    if its concurrency-related, look for a non-thread-safe library being shared across threads. running the worker with one thread temporarily is a quick way to confirm. fingers crossed 🤞

    3 0 helpful
  8. Zora Celik
    @ping_wrangler

    oh ive been there lol exact same thing happened to my old thinkpad last month good luck man!

    2 0 helpful
  9. Sana Grant
    @quartzhound

    my mac is officially haunted. have u checked your linux settings? mine were reset after an update any ideas??

    5 0 helpful
  10. Alba Banerjee
    @alba_cache
    Accepted solution

    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 rebuild elsewhere) often fixes it.

    1 9 helpful
  12. Tariq B.
    @tariqb872

    following, hvaing the same problem

    4 2 helpful
  13. Emeka V.
    @regexworks
    in reply to @alba_cache

    @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.

    1 0 helpful

Reply to this topic

Sign in or create an account to reply.