2008/11/22 Ben Schmidt <[EMAIL PROTECTED]>: > >>> I am aware of bugs with Vim processes that never shut down and I will >>> do what I can to fix these as soon as possible. >> >> I suggest the appcast not be updated until we at least understand this >> bug, and preferably not until it's fixed. Without at least knowing what >> it is, we don't know what other consequences it might have. > >>> If you are having >>> problems with "Vim process leaks" then I advice you to disable >>> "quickstart" for now (and tell me if that does not take care of the >>> problem). > > I don't have quickstart turned on, yet I saw some of the console > messages. I haven't been able to reproduce them yet. But it seems > quickstart just makes the problem more frequent or obvious rather than > actually causing it. I didn't see any until the code of snapshot 37, > though (built from source).
There are two distinct issues here: 1. The one (I think) that you are seeing (and the only one I can reproduce) which causes the following type of error message: com.apple.launchd[78] ([0x0-0x28028].org.vim.MacVim[592]): Stray process with PGID equal to this dead job: PID 627 PPID 1 Vim This goes away if I disable the "Login shell" option so it has something to do with forking new Vim processes. (Google this problem and you'll find heaps of other programs causing launchd to emit this warning.) It seems harmless, but I was hoping it would go away when we ignored SIGCHLD. 2. The more obscure bug that only happens with Quickstart enabled which causes Vim processes to get stuck in a loop where they continuously log the following error: Vim[35947] Exception caught when processing command queue: "connection is invalid" I have never been able to reproduce this. In snap 38 I added a guard that will quit the Vim process if this situation occurs to avoid filling up people's log files. This is the bug I am most concerned about but at least it can be avoided by disabling Quickstart (as far as I know). It also seems to cause a new Vim process to spawn whenever netrw is used (Issue 121). I was thinking of making a build which logs lots of stuff and ask the people who are able to reproduce this bug to run it and tell me what is being logged. At any rate, none of these bugs are critical as I see it (the second one is but you can work around it easily). I don't think they are bad enough for me not to update the appcast (and the second bug is present in snap 36 anyway). Björn --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_mac" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
