Not sure what the issue is here but I have a sneaky suspicion that this is something that was already broken before the change and the change had the effect of turning some undefined behaviour into an outright crash. We've already found a couple of cases where the change of the memory setup caused by this patch has turned 'harmless' memory errors into outright crashers.
That being said, if you're also running git-master Gtk, it could have been this highly related patch which went in right about the same time:
I don't _really_ think this is the case, but this patch changed how the accel label was created and associated with the menu (which is what the backtrace is talking all about) so I thought I'd mention it as a first rule-out.
hi Adam,
Not sure what the issue is here but I have a sneaky suspicion that this is something that was already broken before the change and the change had the effect of turning some undefined behaviour into an outright crash. We've already found a couple of cases where the change of the memory setup caused by this patch has turned 'harmless' memory errors into outright crashers.
That being said, if you're also running git-master Gtk, it could have been this highly related patch which went in right about the same time:
https:/ /git.gnome. org/browse/ gtk+/commit/ ?id=ca0a18918c4 737327a47f8180f 064084ae5a6af1
I don't _really_ think this is the case, but this patch changed how the accel label was created and associated with the menu (which is what the backtrace is talking all about) so I thought I'd mention it as a first rule-out.