Kernel Panic Using emacs and Python (negative open count)

Originator:asmeurer
Number:rdar://13615108 Date Originated:09-Apr-2013 06:03 PM
Status:Duplicate/11340872 Resolved:
Product:OS X Product Version:10.8.3 Build 12D78
Classification:Serious Bug Reproducible:Always
 
09-Apr-2013 06:03 PM Aaron Meurer:
Summary:

Using emacs with certain Python libraries causes the computer to Kernal panic upon closing emacs. 

Steps to Reproduce:

Full details are at https://github.com/tkf/emacs-jedi/issues/37. To reproduce, use test_emacs.el from https://github.com/asmeurer/dotfiles/blob/master/test_emacs.el. You will need to install the various libraries that are added to the load-path (they are all clones of the repos from GitHub).

Then, run 

emacs -Q -l test_emacs.el test.py

And do some typing that activates the auto-completion framework. Then close emacs

Expected Results:

The computer doesn't crash. Everything works normally.

Actual Results:

Mac OS X immediately panics.  This also happens if emacs is force quit, either through kill, by closing the terminal tab, or by force quitting the terminal.

Regression:

This apparently does not occur in Mac OS 10.7, though I have not personally not confirmed this. 

Notes:

Full panic crash report is attached.

If you use M-x epc:controller in emacs, and hit K on each row to manually kill the Python process, it does not panic upon exiting emacs. 

09-Apr-2013 06:03 PM Aaron Meurer:
'test_emacs.el' and 'Kernel_2013-03-19-171057_Aarons-Retina-MacBook-Pro.panic' were successfully uploaded

Comments

GitHub

they are all clones of the repos from GitHub . PC817

By joey899244 at April 11, 2013, 3:25 a.m. (reply...)

The full panic report can be found at the emacs-jedi issue.

By asmeurer at April 10, 2013, 12:07 a.m. (reply...)

Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!