0x0@lemmy.zip to Programmer Humor@programming.dev · 2 months agorace conditionslemmy.zipimagemessage-square87fedilinkarrow-up1883arrow-down125
arrow-up1858arrow-down1imagerace conditionslemmy.zip0x0@lemmy.zip to Programmer Humor@programming.dev · 2 months agomessage-square87fedilink
minus-squarelobut@lemmy.calinkfedilinkarrow-up32·2 months agoNot 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·2 months agoTechnically 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·2 months agoEven safe rust can do it, if we allow compiler bugs
minus-squareapelsin12@lemm.eelinkfedilinkarrow-up10·2 months agoIve also seen this, but not from js but node
minus-squareVitabytesDev@feddit.nllinkfedilinkarrow-up6·2 months agoI have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
minus-squareburlemarx@lemmygrad.mllinkfedilinkarrow-up1·2 months agoYup, 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.