Closed MStraeten closed 2 years ago
A bit strange than bisecting on master & 3.8.x branch gives different result. The 3.8 wrong commit is on tagging.c, seems quite suspicious that this could have introduced an issue with midi devices... Or maybe we have a corrupted memory somewhere and then everything can happen!
This is a duplicate of #10680
i doubt, since i cant reproduce this with my build from Januar 1. darktable-3.8.0+35~gc7dfebcac
backtrace is the same nontheless
it wasn't triggered before on your system probably due to timings (timeout not yet pending when enumeration was happening, reversing the order of some init steps changed the timings).
It looks like on mac SDL2 calls the gtk idle loop during the initialisation of the gamepad module. Since I haven't seen this behavior on any of the platforms I have access to, finding a solution might be a bit of trial and error where I'll depend on you guys to test. Also, I don't have access to any of my midi/gamepad devices this week so won't even be able to test if I break things on linux or windows.
but why this occurs after the merge made today in this case?
Did you update any libraries / dependencies on your machine? The code in the backtrace didn't significantly change for a while/months.
Would you please test if simply adding
if(!darktable.view_manager->current_view) return FALSE;
as the first line of _shortcut_match prevents the issue?
the addition fixes the issue for me - as deleting libSDL2 does - but thats not a solution for those using gamepads ;)
i keep macports quite updated so libraries are frequently updated. But during bisecting i was able to get builds without that issue using the same macports config ...
As I noted in another ticket, that's probably just timings changing a bit - timeout is obviously triggered only if some time has passed.
Either the lib initalisation steps are much faster on the platforms I use/test or the mac is the only platform where libsdl2 behaves like this. Either way, the additional line to test if we actually have an active view, or haven't yet finished initialising, is correct (should have been there -> fixes an oversight/bug) and possibly fixes the only instance where this problem occurs.
latest changes in InputNG introduced following issue:
darktable crashes on start if shortcuts are defined (even no midi shortcuts) and the XTocuh mini is connected:
To Reproduce Please provide detailed steps to reproduce the behaviour, for example:
Which commit introduced the error bisecting in 3.8.x branch gave
bisecting in master gave:
Platform