This happend to me right noww as I tried to write a gui task manager for the GNU/Linux OS

  • Hupf@feddit.org
    link
    fedilink
    arrow-up
    1
    ·
    26 days ago

    My first programming related memory is of the QBasic interpreter.

    I had written some code I was quite happy with, but not saved it yet. As part of a subroutine for sound output, I quickly wrote a loop from 20 to 20000 to output a test signal over 1 second each with that frequency via the PC speaker and hit execute.

    Realizing my mistake, It being MS-DOS and thus single-threaded, I couldn’t Ctrl+C out of it without killing QBasic altogether and losing my code. I couldn’t turn town the PC speaker.

    I ended up closing various doors between the PC and me and waiting it out.

        • bi_tux@lemmy.worldOP
          link
          fedilink
          arrow-up
          2
          ·
          26 days ago

          it didn’t crash the kernel, it just killed every process that isn’t run by the root user, which kind of feels like a crash

        • ulterno@lemmy.kde.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          25 days ago

          There’s this game “HyperRougue”. Run it on Arch.

          hyperrogue-git version 13.0d.r60.g27fb2d92-1

          Go to settings -> 3D configuration -> projection -> projection type -> . Cycle through the projection types. One of them causes something good enough to call a crash.

          I don’t remember anymore if it was just a display driver crash or a kernel crash and I haven’t updated to a newer version (which might have fixed it).

    • N3Cr0@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      26 days ago

      rm -rf <some placeholder>

      Works for . current directory. Yay!

      … also works for / system root. 🔥 Nay!