Crashing during game

[ezpzgg]

I got it to work, but it crashes a lot. Is there a known fix for this or not yet?

[ezpzgg]

CSGO closes automatically at times

[Acew0t]

Same here... What I have especially noticed is when I get into warmup, and get my first kill, then it automatically quits, then quits in-between a few times after...

[amcgregor]

"crashes 'a lot'"
"Quits in-between a few times…"

A lot, randomly, or almost every time it's run? Have you added the compiled executable you're running via sudo to your Security & Privacy System Preference list of apps authorized for full control of your computer? (You shouldn't need to add Terminal.app itself, which would be dangerous, as that would authorize all terminal software you run—all of it—to have full control.) This is required because of what this software does; it writes directly to the memory of another program, which today, operating systems see as anti-social behaviour, and kill. (With extreme prejudice; the app doing the bad behaviour is never notified of being closed, never given a chance to "crash", e.g. produce a core dump, doesn't produce an exit status code—at all—because the macOS kernel is literally deleting the data tracking the process and threads. Poof, it's gone, do not pass go, do not collect $200, that is an ex process. Bereft of life. Shuffled off its mortal coil.)

Also… potential duplicate of #252, #254, and #257 if this is the symptom.

There's the potential other issue that yes, even when operating "perfectly" it can seemingly randomly crash. This is usually a problem amplified by injection into the CS:GO process too early, e.g. before the memory location of the data the hack is looking for have been "fixed in place". These days I tend to inject within a playback session, avoiding sessions which feature player suicide, as that can also trigger a crash. This works ~80% of the time, the remaining time it'll crash once after only a few moments, I'll re-launch, get back to the point of injection, and it'll be fine that time. One thing that doesn't work 90% of the time: injection outside of an active game match. Don't jump the gun.

It crashed, in my last example case, because the memory area for the model list was moved after the hack had thought it had worked it out, and that memory was then reallocated to something else. Apparently, something more critical or sensitive to manipulation.

[amcgregor]

In some diagnostics ("printf school of debugging") it seems the status code associated with the memory write option is never validated or utilized. Outside of a match gives one error, between matches gives another write error, quitting CS:GO doesn't actually quit the hack, which begins getting a third type of error when attempting those writes. Interesting; error handling can definitely be improved. Or included at all.