Open deveee opened 7 years ago
I'm unable to reproduce this particular issue, though I did find that if you add an add-on to a GP, then uninstall the GP, stk doesn't react well
I wasn't able to make a crash, but I somehow added two GPs with the same name :P
I did a few tests messing with the editor, and I was unable to reproduce any of the issues listed here (double-naming, crash, unexpected problems when uninstalling an addon track used in a GP (i.e., besides the GP being disabled)).
It's non-reproducible and didn't happen for a long time, so postpone till later.
after ~1 week no longer see "weird" crashes in google play console, so i assume those issue are fixed (I think multitouch -> update same category by the way)
maybe will these issues after master stk google play is updated
The crash seems to happen still as there's at least one report in public channels referring to the same lines of code in the same files. I also recall crashing once after using GP editor, but, unfortunately, it was too long ago. I couldn't reproduce the crash now, either, even by trying to make a GP with the same tracks as those causing the crash.
Line numbers have changed a bit so I'll post the call stack from 2024 from this post:
Call stack:
edit_gp_screen.cpp:init:180
abstract_state_manager.cpp:popMenu:258
input_manager.cpp:input:1028
event_handler.cpp:OnEvent:212
CIrrDeviceStub.cpp:postEventFromUser:226
CIrrDeviceSDL.cpp:run:1023
main_loop.cpp:run:689
main.cpp:main:2592
crtexe.c:__tmainCRTStartup:341
crtexe.c:WinMainCRTStartup:197
BaseThreadInitThunk
RtlUserThreadStart
---------------------------
OK
---------------------------
It's precisely
states_screens/edit_gp_screen.cpp:176
, which is:Track is null in some cases?