[DiscordArchive] Need help debugging a client crash. I know it's...
[DiscordArchive] Need help debugging a client crash. I know it's...
Original source
I do. I've tried narrowing down breakpoints to see which particular packet is causing the crash, and I've gotten close, but it becomes very hard (for me at least) to get any more resolution out of that area of code, because it's async multithreaded stuff.
rektbyfaith
01-09-2025, 02:03 AM #11Archived author: Ninjapleez • Posted: 2025-01-09T02:03:36.073000+00:00
Original source
I do. I've tried narrowing down breakpoints to see which particular packet is causing the crash, and I've gotten close, but it becomes very hard (for me at least) to get any more resolution out of that area of code, because it's async multithreaded stuff.
Original source
The client is definitely okay with whatever the default state of a warlock pet summon is. While stepping through the code, whichever packet actually spawns the pet goes through okay, causing the pet to show up with an "unknown" name. The pet name packet comes through okay, and the client reflects the name change. But somewhere very near those two causes the crash. Because it's async, sometimes the crash will happen before or after the other two packets come through.
rektbyfaith
01-09-2025, 02:11 AM #12Archived author: Ninjapleez • Posted: 2025-01-09T02:11:50.434000+00:00
Original source
The client is definitely okay with whatever the default state of a warlock pet summon is. While stepping through the code, whichever packet actually spawns the pet goes through okay, causing the pet to show up with an "unknown" name. The pet name packet comes through okay, and the client reflects the name change. But somewhere very near those two causes the crash. Because it's async, sometimes the crash will happen before or after the other two packets come through.
1 Guest(s)
1 Guest(s)