search

ClosestStorm / macvim

Automatically exported from code.google.com/p/macvim
0 stars 0 forks source link

"Object xxx of class NSConcreteData autoreleased with no pool in place" #464

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Summary: after buffers/windows are updated (speculation: by python-based 
plugin), an error message is splashed across the screen in multiple places.  
The message reads (see attached screenshot, transcribing here for 
searchability):

"objc[44179]: Object 0x101585d80 of class NSConcreteData autoreleased with no 
pool in place - just leaking - break on objc_autoreleaseNoPool() to debug"

This occurs *only* when running MacVim in a terminal (either OS X Terminal.app 
or iTerm2 will do) via `mvim -v`.

The plugin I believe is prompting the issue is my fork of vim-fireplace 
(https://github.com/cemerick/vim-fireplace).  It does some perhaps-untoward 
things w.r.t. multithreaded interaction with vim from within python, but 
behaves quite nicely in "headed" MacVim (i.e. launched from the dock or 
double-clicked .app, not in Terminal.app or iTerm).  Either way, I presume the 
resulting error (or at least its delivery?) is a valid bug.

Mac OS X 10.7.5.  Reported behaviour exists under macvim 7.3 and snapshot 68 of 
7.4a.

Original issue reported on code.google.com by c...@cemerick.com on 23 Jul 2013 at 1:53

Attachments:

GoogleCodeExporter commented 9 years ago 
FWIW, a minimal terminal vim (not mvim/gvim, compiled with python support) 
appears to work well with the noted plugin, no redraw errors, etc.

Original comment by c...@cemerick.com on 23 Jul 2013 at 2:38