(Unlikely) potential fork bomb? See below.

second-pair commented 4 years ago

I was testing this out with Superhot and ran into this issue, which required that I hard-power-off my PC. I don't know what caused it, but I believe JSM was the only new factor here, so I've created this ticket in the event that JSM was somehow responsible.

What Happened

I quit Superhot and a series of CMD windows spawned with no text. They seemed to keep spawning in the background until my PC couldn't keep up and slowly ground to a halt. I attempted a shudown with win+x, u, u and waited a minute (while I took a photo), but as expected, nothing happened, so I held the power button to turn my PC off.

What I'd Done (Steps to Reproduce)

Download and unzip JSM (path is ~/Downloads/JSM).
Connect my DS4 controller via Bluetooth.
Start it up.
Disconnect controller from Bluetooth.
RECONNECT_CONTROLLERS
Connect the controller via a wire.
RECONNECT_CONTROLLERS
Drag the provided 'Windows.txt' into the JSM console and hit return.
Play around for a bit.
Go to the Wiki's page for Superhot and copy the code listing.
Open WSL and use Nano to create a new 'SUPERHOT.txt' file under 'GyroConfigs', paste in the copied code.
Drag it into the JSM console and hit return.
Run Superhot through GOG Galaxy and play through a few levels.
Tab out to edit the 'SUPERHOT.txt' file and change some keybindings.
Attempt to re-load the config by dragging it into the JSM consle like before and hitting return. This failed with an error that I can't remember well and can't recognise with a few cursory searches through Atom.

My memory's fuzzy on the order of the following:

Drag the 'Windows.txt' into the JSM console and hit return.
Drag the 'SUPERHOT.txt' into the JSM console and hit return.
Quit Superhot.

After the Superhot window closed, the fork bomb occurred.

What I Tried

Googled JSM causing a fork bomb, no meaningful results found.
Googled Superhot causing a fork bomb, no meaningful results found.
Search the local JSM directory, as well as folders in ~/AppData, for anything resembling a logfile.
Clone the JoyShockMapper main repo and use Atom to do a "Find in project" for 'log' and reviewed each result to see if they indicated a logfile - nothing found.
Read through the Superhot logs, which only seem to have initialisation information in them.

The Photo I Took Before Powering Down

FWIW, here's the photo I took on my phone after I'd lost control of my PC. Mainly just to provide (noisy) context for the description ^. IMG_E9931

Sorry for the lack of useful detail, but I wasn't sure what to do next! I've not opened JSM again, in case logs are kept somewhere that might get overwritten. If the programme does keep logs, do let me know where and I'll fish them out. Otherwise, let me know if there's anything else I can do to help, or feel free to do whatever with this ticket if it's not useful.

SharlSherif commented 4 years ago

I got the same issue by running main.cpp using g++ on Win10.

JibbSmart commented 4 years ago

Thank you for sharing in all this detail, @second-pair, and thank you @SharlSherif for corroborating. I'll see if I can find anything. JSM doesn't log anything. It also doesn't fork, and I'm pretty sure it only requests a console window once at the beginning of main, so I don't know how this could happen, but I'll look into it more deeply soon.

SharlSherif commented 4 years ago

@JibbSmart Can you take a look at my issue here :https://github.com/JibbSmart/JoyShockMapper/issues/52

JibbSmart / JoyShockMapper