0x0@lemmy.zip to Programmer Humor@programming.dev · 3 个月前race conditionslemmy.zipimagemessage-square87fedilinkarrow-up1887arrow-down125
arrow-up1862arrow-down1imagerace conditionslemmy.zip0x0@lemmy.zip to Programmer Humor@programming.dev · 3 个月前message-square87fedilink
minus-squarelobut@lemmy.calinkfedilinkarrow-up32·3 个月前Not a word of a lie, I saw a “segmentation fault” error in JavaScript. Can’t remember how we resolved it, but it did blow my mind.
minus-squarejj4211@lemmy.worldlinkfedilinkarrow-up12·3 个月前Technically any language runtime can end in a segmentation fault. For some languages, in principle this shouldn’t be possible, but the runtimes can have bugs and/or you are calling libraries that do some native code at some point.
minus-squareGagootron@feddit.orglinkfedilinkarrow-up7·3 个月前Even safe rust can do it, if we allow compiler bugs
minus-squareapelsin12@lemm.eelinkfedilinkarrow-up10·3 个月前Ive also seen this, but not from js but node
minus-squareolenko@feddit.nllinkfedilinkarrow-up6·3 个月前I have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
minus-squareburlemarx@lemmygrad.mllinkfedilinkarrow-up1·3 个月前Yup, can confirm. We had a wrapper to a C++ library using JNI, so whenever this library crashed so did the entire JVM.
Not a word of a lie, I saw a “segmentation fault” error in JavaScript.
Can’t remember how we resolved it, but it did blow my mind.
Technically any language runtime can end in a segmentation fault.
For some languages, in principle this shouldn’t be possible, but the runtimes can have bugs and/or you are calling libraries that do some native code at some point.
Even safe rust can do it, if we allow compiler bugs
Ive also seen this, but not from js but node
I have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
Yup, can confirm. We had a wrapper to a C++ library using JNI, so whenever this library crashed so did the entire JVM.