|
From: | Pip Cet |
Subject: | bug#21380: 25.0.50; GTK-induced segfault when scheduling timer from window-configuration-change-hook |
Date: | Tue, 1 Sep 2015 20:48:18 +0000 |
> The only code path that I see that's potentially dangerous is that atimers
> appear to be executed even if input is blocked.
Yes, that's exactly what bothered me. Not calling QUIT prevents that.
Alternatively, we could turn off atimers (by calling turn_on_atimers)
while Fcopy_sequence runs.
0001-Fix-potential-race-conditions-Bug-21380.patch
Description: Text Data
[Prev in Thread] | Current Thread | [Next in Thread] |