search

edenzik / macvim

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

Crash during general system slowness #187

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I hit cmd-o, which opened the open file dialog, which then beachballed a 
bit (loading file info etc; my system was quite loaded). After a few seconds 
of beachballing in the open file dialog, MacVim decided to crash. Perhaps 
Vim was getting impatient because MacVim was hung in the open file 
dialog?

Console.app:

6/17/09 12:22:45 AM ReportCrash[67775] Formulating crash report for 
process MacVim[16785] 
6/17/09 12:22:45 AM Vim[57430] WARNING[connectionDidDie:]: Main 
connection was lost before process had a chance to terminate; preserving 
swap files. 
6/17/09 12:22:46 AM Vim[66800] WARNING[connectionDidDie:]: Main 
connection was lost before process had a chance to terminate; preserving 
swap files. 
6/17/09 12:22:48 AM ReportCrash[67775] Saved crashreport to 
/Users/thakis/Library/Logs/CrashReporter/MacVim_2009-06-17-
002238_thakis-macbookpro.crash using uid: 54011 gid: 5000, euid: 
54011 egid: 5000 
6/17/09 12:22:48 AM ReportCrash[67775] Saved crashreport to 
/Users/thakis/Library/Logs/CrashReporter/MacVim_2009-06-17-
002238_thakis-macbookpro.crash using uid: 54011 gid: 5000, euid: 
54011 egid: 5000 

The crashreport is attached.

Nico

Original issue reported on code.google.com by thakis@chromium.org on 17 Jun 2009 at 7:27

Attachments:

GoogleCodeExporter commented 9 years ago 
There is not good way to reproduce I suppose?

I think the problem may be that I pass key equivalents on to the main menu 
explicitly and Cocoa does not seem 
to like that (although it works and it is a public API).  They have changed key 
equivalent handling in Leopard so 
that I could get rid of that hack and that may take care of it but I do not 
know for sure so it would be good to 
have some way of testing it.

Original comment by bjorn.winckler@gmail.com on 18 Jun 2009 at 4:10

GoogleCodeExporter commented 9 years ago 
No, I can't reproduce this, sorry. Since I've only seen this problem once, it's 
probably not 
the most important thing to worry about. Just wanted to make sure it's in the 
records.

Original comment by thakis@chromium.org on 18 Jun 2009 at 4:25