Re: Alternative workaround to macOS SIGABRT on exit?
Richard Kimberly Heck <[email protected]>
| Newsgroups | gmane.editors.lyx.devel |
|---|---|
| Message-ID | <[email protected]> |
On 3/18/26 9:52 AM, Pavel Sanda wrote: > On Wed, Mar 18, 2026 at 08:54:22AM +0100, Scott Kostyshak wrote: >> On lyx-users Anders reports that the following does not trigger the >> issue: >> >> command-sequence buffer-close-all; lyx-quit >> >> This suggests the idea that we can just call buffer-close-all inside of >> lyx-quit, as done in the attached patch. >> >> Any thoughts? > That would be nice if it works. However the workaround might need to be little > more sophisticated so it's equivalent for the sequence Quit->Save?->Cancel. My own hope is that this information will lead to a discovery of why we're really seeing this crash, though Scott's patch looks much preferable to the existing workaround. My guess would be that it's some kind of race condition: The LyX application can close before the buffers have been closed. Why that might be, though, I have no idea. But maybe Qt is responding to signals in some threaded way? Riki -- lyx-devel mailing list [email protected] https://lists.lyx.org/mailman/listinfo/lyx-devel