[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#30364: 26.0.91; thread crash on macos

From: Aaron Jensen
Subject: bug#30364: 26.0.91; thread crash on macos
Date: Sat, 17 Feb 2018 10:40:10 -0800

On Sat, Feb 17, 2018 at 10:17 AM, Eli Zaretskii <address@hidden> wrote:
> When this crashes, is one of the threads you launched always doing GC,
> like in the first backtrace you've shown?

I can tell this by the mark_object/mark_vectorlike calls in the stack,
right? If so, yes, it appears so.

> Btw, I'm not really sure what you are doing and why: what is the
> purpose of launching 100 threads all doing the same job with the same
> data?

Ultimately, I was trying to port company-dabbrev to use threads. I
noticed the crash while working on it, so the 100 threads at the same
time was just a way of more consistently reproducing it. I could
probably have run the 100 threads serially to reproduce it, I don't

On Sat, Feb 17, 2018 at 10:23 AM, Alan Third <address@hidden> wrote:
> Can you try the Main Thread Checker to see if it’s doing some UI stuff
> outside of the main thread?

I don't know what this is, but I do know that there are
(input-pending-p)'s in the thread from the current implementation.
They don't need to be there (i guess they'd be replaced by
thread-yields, but when I did that it got very slow). I don't have
time to test if removing those fixes the crashes just yet, but could
that be causing the crash? The thread also calls `message`, I don't
know if that's considered "UI stuff"


reply via email to

[Prev in Thread] Current Thread [Next in Thread]