|
From: | Daniel Colascione |
Subject: | bug#30364: 26.0.91; thread crash on macos |
Date: | Mon, 19 Feb 2018 09:29:49 -0800 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 |
On 02/19/2018 09:24 AM, Paul Eggert wrote:
What about just dedicating a thread to GC? We'd create it and have it wait on a condition variable. Any thread could signal the CV, block, and wait for GC to complete. It'd be pretty simple, I think, and unlike the "always GC on main thread" proposal, it wouldn't force everything on the main thread to be interruptible.Eli Zaretskii wrote:Would you like me to vary it based on 32-bit vs 64-bit?I think so, but I'd like to hear from others about this. Paul, Andreas, could you please comment?A 64-bit Emacs should need more stack space than a 32-bit Emacs, yes. It wouldn't be double the space, since not everything on the stack is a pointer or an EMACS_INT. If you really want to fine-tune it you can also depend on the width of EMACS_INT. Getting it "just right" would be a bit tricky.8 MiB/thread for 64-bit Emacs sounds OK to me. I wouldn't cheap out on 64-bit platforms.
[Prev in Thread] | Current Thread | [Next in Thread] |