Memory leaks froze my pc about sc-im HOT 6 CLOSED

Hello. Why you say there is a leak? Did you run sc-im with Valgrind or other tool and saw this?

from sc-im.

Because I have run plenty of wild/random software, and my linux has never behaved this way before. Never before have I experienced input freeze (something which is normal in Windows with certain unoptimized programs)
Even if I run an infinite loop in bash, I can just kill the window (dwm), it wouldn't corrupt my entire pc (and on reboot it said something about RAM)

Here is the argument for memory leak, without the usage of any software: It completed the first time without issues, and since unit tests are supposed to be deterministic, it doesn't make sense for the 2nd time to cause issues. This means the state of the computer changed, and this can be true only if the memory was changed, hence my assumption for memory leak. If it wasn't a memory leak, with the same input, there should be the same output ;)

from sc-im.

I run all these tests with valgrind without any memory leaks in the log shown. please rerun those tests with valgrind and report back. if there is a memory leak you should see it in the log. thanks.

from sc-im.

It sounds like a case of "it works on my machine"
I refuse to run that script again, as it was harmful to my hardware. Solving a bug by risking my entire computer + the time I have spent on configuring it is just not worth it.

If you wish, close this issue, I only wanted to report this bug.

from sc-im.

from sc-im.

I agree with @luna-in-space. @TheYellowArchitect if you happen to run these with valgrind, please share the log. thanks again.

from sc-im.