0x0@lemmy.zip to Programmer Humor@programming.dev · 14 days agorace conditionslemmy.zipimagemessage-square62linkfedilinkarrow-up1785arrow-down124
arrow-up1761arrow-down1imagerace conditionslemmy.zip0x0@lemmy.zip to Programmer Humor@programming.dev · 14 days agomessage-square62linkfedilink
minus-squarelobut@lemmy.calinkfedilinkarrow-up23·14 days 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-squareapelsin12@lemm.eelinkfedilinkarrow-up10·13 days agoIve also seen this, but not from js but node
minus-squarejj4211@lemmy.worldlinkfedilinkarrow-up9·13 days 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-squareVitabytesDev@feddit.nllinkfedilinkarrow-up6·13 days agoI have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
minus-squareburlemarx@lemmygrad.mllinkfedilinkarrow-up1·13 days 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.
Ive also seen this, but not from js but node
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.
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.