[MacPorts] #52831: emacs-app @24.5_3+inline: Emacs hangs when I edit LaTeX files (Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'nextEventMatchingMask should only be called from the Main Thread!')
MacPorts
noreply at macports.org
Mon Nov 7 04:08:28 CET 2016
#52831: emacs-app @24.5_3+inline: Emacs hangs when I edit LaTeX files (Terminating
app due to uncaught exception 'NSInternalInconsistencyException', reason:
'nextEventMatchingMask should only be called from the Main Thread!')
----------------------+--------------------------------
Reporter: iqgrande | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Keywords: | Port: emacs-app
----------------------+--------------------------------
Greetings:
My Emacs app has been hanging on my ever since I updated to macOS Sierra
(I followed the instructions on Migrating and re-built everything from
scratch including emacs-app). When it hangs, I am able to obtain the
following error.
{{{
2016-11-06 19:13:28.288 Emacs[3460:2384600] *** Terminating app due to
uncaught exception 'NSInternalInconsistencyException', reason:
'nextEventMatchingMask should only be called from the Main Thread!'
*** First throw call stack:
(
0 CoreFoundation 0x00007fff8b14848b
__exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fff9f8aacad
objc_exception_throw + 48
2 AppKit 0x00007fff8945b50c
-[NSApplication(NSEvent) shouldBeTreatedAsInkEvent:] + 0
3 Emacs 0x0000000100172958
ns_send_appdefined + 103
4 Emacs 0x0000000100175397
-[EmacsApp fd_handler:] + 668
5 Foundation 0x00007fff8cacc30d
__NSThread__start__ + 1243
6 libsystem_pthread.dylib 0x00007fffa03a0aab
_pthread_body + 180
7 libsystem_pthread.dylib 0x00007fffa03a09f7
_pthread_body + 0
8 libsystem_pthread.dylib 0x00007fffa03a0221
thread_start + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException
}}}
Google helped me find Emacs bug 23924 [https://lists.gnu.org/archive/html
/bug-gnu-emacs/2016-07/msg01177.html], which appears to be this issue as
well. Within that thread, a developer, I think, created a patch and it
appears to have been verified to work. I think the patch was for 25.1.50.
Any assistance you can provide would be much appreciated. It's possible
that updating the port from 24.5 to 25.1 may fix this issue if the patch
had been applied. Please let me know if you have any questions, comments,
or concerns. Thank you for your help with this.
Kind regards,
Anthony
--
Ticket URL: <https://trac.macports.org/ticket/52831>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list