moving MacVim window causes reproducible System Crash

[GoogleCodeExporter]

What steps will reproduce the problem?

Moving the Macvim window to the extreme upper left corner of my secondary
monitor causes OS X to beachball and be completely unresponsive.

What is the expected output? What do you see instead?

I expect the window to move past the upper left corner.

What version of the product are you using? On what operating system?

MacVim version 26, OS X 10.5.2, 17-inch macbook pro with a 24" external
monitor.

Please provide any additional information below.

The external monitor is positioned to the left and slightly above the
macbook monitor. MacVim had run nonstop in heavy usage for a week and a
half without issue until I found this one. 

I suspect it's an infinite loop caused by a negative coordinate issue, but
that's just a dumb guess. I can move all my other windows past the extreme
upper left corner without issue.

Let me know if there's anything I can do to help you debug this; I'm a
coder but I know nothing about Cocoa or Objective-c.

Original issue reported on code.google.com by bill.m...@gmail.com on 16 Apr 2008 at 7:50

[GoogleCodeExporter]

It would be immensly helpful if you can compile MacVim yourself, run it through 
the 
debugger and try to see what is going on.  I doubt I'll ever be able to 
reproduce 
this bug since I haven't got two monitors.

Let me know what you find out,
Bjorn

Original comment by bjorn.winckler@gmail.com on 16 Apr 2008 at 10:28

[GoogleCodeExporter]

Will do, when I get into work tomorrow. Does one use XCode to debug these sorts 
of
things? I see the build instructions, but don't know how to debug it.

Original comment by bill.m...@gmail.com on 16 Apr 2008 at 10:32

[GoogleCodeExporter]

You use gdb. If you like GUIs then you can debug with Xcode (it had a frontend 
for gdb). Just remember to 
build with the "Debug" configuration. 

Original comment by bjorn.winckler@gmail.com on 17 Apr 2008 at 2:58

[GoogleCodeExporter]

Well, crap, I got everything built and then the bug went away. I reproduced the 
bug
three times in a row.

I've got the debug build all set up, so if it happens again I'll be able to dig 
in.

Sorry for the not-helpfulness.

Original comment by bill.m...@gmail.com on 17 Apr 2008 at 1:35

[GoogleCodeExporter]

I know the situation... :/

Let me know if you ever gain any insight as to what's going on.

Original comment by bjorn.winckler@gmail.com on 17 Apr 2008 at 8:20

[GoogleCodeExporter]

I have experienced a similar problem, but not as predictable - sometimes when I 
try
to move the macvim window the system becomes unresponsive. If I'm listening to 
music
it will still play, and the mouse can still be moved, but otherwise the system 
will
not respond, and I need to hard reboot.

I don't expect you can do much to figure this one out without more specific
information, just letting you know that it's an issue.

I'm running 5.2

Original comment by ac1...@gmail.com on 28 May 2008 at 10:52

[GoogleCodeExporter]

It really baffles me that moving a window would cause OS X to beachball.  The 
only thing that MacVim does when 
you move a window is to store the window position in the user defaults database 
(see -[MMWindowController 
windowDidMove:]).

Anyway, please look inside "~/Library/Logs/CrashReporter/" for any logs whose 
filename starts with "MacVim" or 
"Vim".  There should be at least one...open it up and look for the date around 
where MacVim crashed because of 
moving a window and copy the information from that crash and email it to me.  
(You could email the entire file 
unless it is too large.)  Thanks.

Original comment by bjorn.winckler@gmail.com on 28 May 2008 at 7:47

[GoogleCodeExporter]

This has happened to me on several occasions as well. Unfortunately, I have no 
way of
reproducing this predictably. I will post available logs if this happens again,
although I am not sure if any logs are going to be produced, because this 
usually
causes a system lockup/need to hard reboot for me. 

Original comment by ngaloppo@gmail.com on 14 Jun 2008 at 3:10

[GoogleCodeExporter]

I am in the middle of debugging another bug that's causing MacVim to crash.  
With a bit of luck, this one is 
related to it so be on the look out for this bug in the next snapshot (which 
will be released when I fix that bug) 
and if it's still there, please let me know.  Thanks.

Original comment by bjorn.winckler@gmail.com on 18 Jun 2008 at 8:33

[GoogleCodeExporter]

Since there's so much activity on this, I'll just report that in my case the 
problem
has not recurred since April 16th, despite having done the same thing that 
seemed to
cause it many times in between (I even try it intentionally every once in a 
while,
trying to make the bug reproduce, no luck).

Original comment by bill.m...@gmail.com on 18 Jun 2008 at 1:22

[GoogleCodeExporter]

I have also observed the graphics hang from comment 6, when using snapshot 36 
on OSX
10.5.5.  Most often it occurs when I drag a MacVim window which is on my 
secondary
monitor (incidentally, also to the left of my MacBook, as in the initial report)
which partially obscures Firefox 3 or another MacVim window and I try to move 
one of
the MacVim ones.  I am not ending up anywhere near the upper-left-hand corner, 
but
perhaps the bottom of the MacVim window does extend below the primary screen's 
bottom.

The machine is still alive (I can ssh in), and information does get saved to 
the log.
 It just appears that the display is frozen.  I'm attaching the relevant portion of
the logs for it.  It happens perhaps once every two weeks with heavy usage.  
There is
no associated log in the CrashReporter directory.

Original comment by tsha...@gmail.com on 21 Oct 2008 at 7:59

Attachments:

• macvim_crash.txt

[GoogleCodeExporter]

The graphics crash from comment 6 (which I first noticed in comment 11) still 
exists
in snapshot 39, with pretty much the same symptoms.

Original comment by tsha...@gmail.com on 8 Dec 2008 at 8:14

[GoogleCodeExporter]

(just thought I'd say that I still have not seen this crash since Apr 16 despite
heavy daily usage, and suspect that the others are reporting a slightly 
different
issue than I was)

Original comment by bill.m...@gmail.com on 8 Dec 2008 at 8:21

[GoogleCodeExporter]

Thanks for keeping me updated on this issue.  I still have no clue as to what 
is causing this, but there more 
information I get the better.

tshatch: What is that "macvim_crash.txt" log?  I looked at it and it means 
nothing to me.  As far as I can gather 
MacVim doesn't crash -- only the display "locks up"...is that correct?  Does it 
only happen when you move 
MacVim windows?

Original comment by bjorn.winckler@gmail.com on 9 Dec 2008 at 4:10

[GoogleCodeExporter]

I've just experienced a lock up similar to comment 11 myself twice now (I 
didn't confirm that it was possible to 
ssh in to the machine, but it appeared to be running but the screen was 
"frozen" so I could not do else than to 
hold down the power button to reboot).  Both times the screen locked up when I 
was running the debugger 
under Xcode.  Of course, MacVim was open too (as it always is for me ;) but the 
crash happened just as gdb 
finished loading.  Could it be that this is not a bug that is caused by MacVim?

Original comment by bjorn.winckler@gmail.com on 13 Dec 2008 at 12:03

[GoogleCodeExporter]

I have confirmed that the screen freezing bug is caused by gdb on my machine:

1. One of my projects (not MacVim) has a tendency to crash all the time, when 
it does gdb starts and attaches 
to the process.  As soon as gdb has finished loading the screen freezes 
(there's a 2 s delay or so during which 
time I can switch to another window).

2. When "frozen" I cannot click on any windows, change "Space", bring up the 
"Force Quit Applications" dialog 
or anything.  However, my wireless mouse/keyboard seem to pop in and out (the 
"Connection lost" picture 
sometimes appear on screen).  Also, the wireless connection status icon (in the 
menu bar) seems to work.

3.  ssh:ing to the machine from another is possible.  If I "ps aux | grep gdb" 
and then kill that process the 
computer is responsible yet again and everything is back to normal!

So, to those of you who experience screen "freezes": try to ssh into the 
machine and kill any MacVim/Vim 
processes.  Does that restore the computer?  If not, try to kill all other user 
processes one by one to see which 
the offender might be.  Please let me know what you find out.

Original comment by bjorn.winckler@gmail.com on 14 Dec 2008 at 1:10

[GoogleCodeExporter]

As an aside: I did not even have MacVim running when I was performing the 
"experiment" outlined in Comment 
16.

Original comment by bjorn.winckler@gmail.com on 14 Dec 2008 at 1:11