0x0@lemmy.zip to Programmer Humor@programming.dev · 18 days agorace conditionslemmy.zipimagemessage-square67fedilinkarrow-up1827arrow-down124
arrow-up1803arrow-down1imagerace conditionslemmy.zip0x0@lemmy.zip to Programmer Humor@programming.dev · 18 days agomessage-square67fedilink
minus-squarelobut@lemmy.calinkfedilinkarrow-up28·18 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-squarejj4211@lemmy.worldlinkfedilinkarrow-up11·17 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-squareapelsin12@lemm.eelinkfedilinkarrow-up10·17 days agoIve also seen this, but not from js but node
minus-squareVitabytesDev@feddit.nllinkfedilinkarrow-up6·17 days agoI have seen a Java program I wrote terminate with SIGSEGV. I think a library was causing it.
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.
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.