Open kreuzerkrieg opened 3 years ago
On some Win10 systems it crashes with access violation and creates a dump, this is a call stack I was able to pull out
Debug build did not yield more informative callstack, looks like symbol info was stripped Any ideas?
0000000000000000() MagicaVoxel.exe!00007ff6f54b6c9b() MagicaVoxel.exe!00007ff6f54c2a9d() MagicaVoxel.exe!00007ff6f54c55fc() MagicaVoxel.exe!00007ff6f54c4cfa() MagicaVoxel.exe!00007ff6f54c4c03() MagicaVoxel.exe!00007ff6f55a7342() MagicaVoxel.exe!00007ff6f54cb9de() MagicaVoxel.exe!00007ff6f54cb95d() MagicaVoxel.exe!00007ff6f54c16a0() MagicaVoxel.exe!00007ff6f54bf112() user32.dll!00007ffadb98e858() user32.dll!00007ffadb98e4ee() opengl32.dll!00007ffaae34f950() user32.dll!00007ffadb98e858() user32.dll!00007ffadb98e3dc() user32.dll!00007ffadb9a0bc3() ntdll.dll!00007ffadc830a44() win32u.dll!00007ffad9fb1124() user32.dll!00007ffadb98df33() user32.dll!00007ffadb98cbc3() user32.dll!00007ffadb98c2af() uxtheme.dll!00007ffad797b8d9() uxtheme.dll!00007ffad797b2c1() user32.dll!00007ffadb98c7e3() MagicaVoxel.exe!00007ff6f54c16f1() MagicaVoxel.exe!00007ff6f54bf112() user32.dll!00007ffadb98e858() user32.dll!00007ffadb98e4ee() opengl32.dll!00007ffaae34f950() user32.dll!00007ffadb98e858() user32.dll!00007ffadb98e3dc() user32.dll!00007ffadb9a5bf0() ntdll.dll!00007ffadc830a44() win32u.dll!00007ffad9fb1be4() MagicaVoxel.exe!00007ff6f54bfac1() MagicaVoxel.exe!00007ff6f54cc174() MagicaVoxel.exe!00007ff6f54e7251() MagicaVoxel.exe!00007ff6f54e6fcc() MagicaVoxel.exe!00007ff6f54e6f4a() MagicaVoxel.exe!00007ff6f54cf64c() MagicaVoxel.exe!00007ff6f54c5aed() MagicaVoxel.exe!00007ff6f54cc38e() MagicaVoxel.exe!00007ff6f55ad0ef() MagicaVoxel.exe!00007ff6f553551c() MagicaVoxel.exe!00007ff6f553273c() MagicaVoxel.exe!00007ff6f5542f95() MagicaVoxel.exe!00007ff6f55a60bf() MagicaVoxel.exe!00007ff6f54c2048() MagicaVoxel.exe!00007ff6f54cb7ed() MagicaVoxel.exe!00007ff6f54bf75e() MagicaVoxel.exe!00007ff6f55b02b1() MagicaVoxel.exe!00007ff6f55b057e() MagicaVoxel.exe!00007ff6f56853ab() kernel32.dll!00007ffadb607034() ntdll.dll!00007ffadc7e2651()
Ok, apparently the crash is due to missing/broken OpenGL driver I think there is a better way to tell that to user than just creating dump :)
On some Win10 systems it crashes with access violation and creates a dump, this is a call stack I was able to pull out
Debug build did not yield more informative callstack, looks like symbol info was stripped Any ideas?