Frequent Crashes (Linux)
|
I'm posting this in hope that it will help GGG to fix some bugs.
I've been experiencing very frequent crashes in the campaign. Last league it worked perfectly fine and I was using the exact same setup. My specs: - Operating System: Nobara Linux 43 - Kernel Version: 6.19.5-200.nobara.fc43.x86_64 (64-bit) - Processor: Intel Core i7-8700K CPU @ 3.70GHz - Memory: 16 GiB of RAM - Graphics Processor: NVIDIA GeForce RTX 5070 What I've tried so far: - Updating all drivers - Changing from Vulcan to DirectX12 - Deleting the Shader Cache and verifying game integrity via Steam - Setting Texture Quality from High to Medium - Disabling Multithreading - Changing from Windowed Fullscreen to Fullscreen Nothing has helped so far. Thanks to everyone reading this. :-) Last bumped on Mar 12, 2026, 10:37:19 AM
|
|
|
Does the Proton log record anything potentially meaningful?
Less likely though it may be, does Path of Exile's own log file capture anything? GGG do not offer first-party Technical Support.
Free Technical Support guides created by the community are available here: https://www.poecommunity.help No ads, trackers, or other weird stuff. |
|
" Do you know where to find the Proton log? I also just started to get frequent crashes on POE after having no issues since league launch. I am on Bazzite, and I run POE thru Heroic Games Launcher. There is nothing unusual in the logs there, but I don't know where to find any Proton specific log. |
|
" Thank you for your answer! Since yesterday the situation has improved and I get less crashes. Maybe it's due to the hotfix. Edit: now it's back to crashing very often I'm new to Linux so I hope I set up the Proton log correctly. I played till it crashed a few more times and three things stand out in the log. a lot of errors in red like: 1932.391:013c:0184:err:font:alloc_font_handle out of realized font handles some in orange like: 13804.022:013c:0194:warn:seh:virtual_unwind backtrace: 00000001401D04A1: L"PathOfExileSteam.exe" + 00000000001D04A1. the last lines after a crash are always something like this: 17489.896:0124:0154:trace:seh:RtlRestoreContext returning to 00006FFFFF9126EA stack 0000000003EAFAC0 17489.897:0124:0154:trace:mscoree:DllMain (00006FFFFDDD0000, 3, 0000000000000000) 17489.897:0124:048c:trace:unwind:RtlGrowFunctionTable 0000000003C03A50, 55 17489.899:0124:048c:trace:unwind:RtlGrowFunctionTable 0000000003C03A50, 56 17489.899:0124:048c:trace:unwind:RtlGrowFunctionTable 0000000003C03A50, 57 17489.900:0124:0128:trace:unwind:RtlGrowFunctionTable 0000000003C03A50, 58 17489.900:0124:0128:trace:unwind:RtlGrowFunctionTable 0000000003C03A50, 59 17489.900:0124:0128:trace:unwind:RtlGrowFunctionTable 0000000003C03A50, 60 17489.904:0124:048c:trace:mscoree:DllMain (00006FFFFDDD0000, 3, 0000000000000000) 17489.904:0124:0490:trace:mscoree:DllMain (00006FFFFDDD0000, 3, 0000000000000000) 17489.904:0124:0168:trace:mscoree:DllMain (00006FFFFDDD0000, 3, 0000000000000000) 17489.905:0124:0494:trace:mscoree:DllMain (00006FFFFDDD0000, 3, 0000000000000000) 17489.954:0124:0128:trace:mscoree:_CorDllMain (0000000004CD0000, 0, 0000000000000001) 17489.954:0124:0128:trace:mscoree:_CorDllMain (0000000004660000, 0, 0000000000000001) 17489.954:0124:0128:trace:mscoree:_CorDllMain (0000000004610000, 0, 0000000000000001) 17489.956:0124:0128:trace:mscoree:_CorDllMain (0000000003C90000, 0, 0000000000000001) 17489.956:0124:0128:trace:mscoree:_CorDllMain (0000000003C70000, 0, 0000000000000001) 17489.956:0124:0128:trace:mscoree:_CorDllMain (0000000010000000, 0, 0000000000000001) 17489.956:0124:0128:trace:mscoree:_CorDllMain (0000000002E40000, 0, 0000000000000001) 17489.957:0124:0128:trace:mscoree:DllMain (00006FFFFDDD0000, 0, 0000000000000001) pid 22182 != 22181, skipping destruction (fork without exec?) Also twice I had an error message: Detected Corrupted Game Files Last edited by Camelot#4638 on Mar 12, 2026, 10:39:32 AM
|
|
" Hi If I did it correctly, I set up Proton log with the launch option: PROTON_LOG=1 %command% The log file itself was in my home directory. |
|























