Subject: bug#16901: 24.3.50; emacs_backtrace.txt

From: Dmitry Antipov <[email-masked]>
Date: Fri, 28 Feb 2014 16:21:25 +0400

On 02/28/2014 02:43 PM, Eli Zaretskii wrote:

>> From: Juanma Barranquero <[email-masked]>
>> Date: Fri, 28 Feb 2014 10:41:48 +0100
>> Cc: [email-masked]
>>
>> w32_backtrace at w32fns.c:8431
>> emacs_abort at w32fns.c:8463
>> terminate_due_to_signal at emacs.c:378
>> die at alloc.c:6761
>> compact_small_strings at alloc.c:1960
>> sweep_strings at alloc.c:1890
>> gc_sweep at alloc.c:6333
>> Fgarbage_collect at alloc.c:5572
>> maybe_gc at lisp.h:4518
>
> Thanks.
>
> Dmitry, any insights?

As usual, it's hard to say anything without a clean recipe to reproduce.
I realize that GC-related bugs may be very subtle, so all affected users
(especially on MS-Windows and OSX) are pleased to bisect at least; r114795
may be a good starting point.

Now we have an explanation of http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16069.
Suggested fix should help http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16817#5
as well; unfortunately this is X-specific and probably won't help with weird GC
issues on other platforms.

Dmitry