PathOfExileClient terminated unexpectedly, StackOverflow link to resolve issue

"


...snip...

Crashed Thread: 17

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: PathOfExileClient [29775]

Application Specific Information:
abort() called

...snip...

Thread 17 Crashed:
0 ??? 0x7ff8ab99e9a8 ???
1 libsystem_kernel.dylib 0x7ff81bd531e2 __pthread_kill + 10
2 libsystem_pthread.dylib 0x7ff81bd8aee6 pthread_kill + 263
3 libsystem_c.dylib 0x7ff81bcb1b45 abort + 123
4 libc++abi.dylib 0x7ff81bd45282 abort_message + 241
5 libc++abi.dylib 0x7ff81bd373fb demangling_terminate_handler() + 267
6 libobjc.A.dylib 0x7ff81ba0ba6f _objc_terminate() + 104
7 libc++abi.dylib 0x7ff81bd446db std::__terminate(void (*)()) + 6
8 libc++abi.dylib 0x7ff81bd47123 __cxa_rethrow + 99
9 PathOfExileClient 0x10515d8dd 0x102f80000 + 35510493
10 PathOfExileClient 0x10516247a 0x102f80000 + 35529850
11 PathOfExileClient 0x1051622b0 0x102f80000 + 35529392
12 libsystem_pthread.dylib 0x7ff81bd8b1d3 _pthread_start + 125
13 libsystem_pthread.dylib 0x7ff81bd86bd3 thread_start + 15




Per this StackOverflow link, https://stackoverflow.com/questions/28757161/can-a-terminate-handler-throw-an-exception, when `__cxa_rethrow` calls `std::_terminate` (as we see in the stack dump above), then it's because somewhere in the C++ code you're calling `throw;` instead of `throw theException;`. I can't tell you where in the code this bug is because I don't have your debugging symbols.

Considering that SO post, you could probably grep the source code for "throw;" and look for the area around character creation and also the area around character selection.

Hopefully, this detective work helps accelerate your debugging.

btw, this is on the MacOS client.
Last bumped on Jul 30, 2024, 11:19:17 PM
This thread has been automatically archived. Replies are disabled.

Report Forum Post

Report Account:

Report Type

Additional Info