Opened 8 years ago

Closed 8 years ago

#52831 closed defect (fixed)

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!')

Reported by: iqgrande Owned by: drkp (Dan Ports)
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: Cc:
Port: emacs-app

Description

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

Change History (4)

comment:1 Changed 8 years ago by mf2k (Frank Schima)

Cc: hum@… removed
Owner: changed from macports-tickets@… to hum@…
Status: newassigned

comment:2 Changed 8 years ago by drkp (Dan Ports)

Owner: changed from hum@… to drkp

I haven't tested on Sierra yet; is this still an issue with 25.1?

comment:3 Changed 8 years ago by iqgrande

It appears to be working fine now. Please close the ticket for now and if the issue comes back, then we can re-open it. Thank you for updating the port.

comment:4 Changed 8 years ago by drkp (Dan Ports)

Resolution: fixed
Status: assignedclosed

Great, thanks for the update.

Note: See TracTickets for help on using tickets.