On Mon, Jul 10, 2006 at 20:52:00 +0100, Ron Blaschke wrote: > Bram Moolenaar wrote: > > Soon-Ping Phang wrote: > > > >> I'm trying to determine whether I should submit a bug > >> report for a problem I encountered or if one was > >> already submitted. > >> > >> Basically, I'm finding that if I paste a long line of > >> text (4650+ characters) into an 80x25 Vim window (v7.0 > >> on WinXP), and then, while leaving the cursor at the > >> end of the line, maximize the window, Vim crashes. > >> > >> Has anyone encountered this before? > > > > I don't think this was reported before. Please describe the environment > > in which this happens. Preferably without any personal settings, start > > Vim with "-u NONE". > > I experienced this too, some time ago, but didn't worry because I rarely > work with such long lines. At least on my system I can reproduce this > with 7.0 on my Windows XP box. > > Start gvim > gvim -u NONE > > Insert 5000 characters, e.g. '-' > 5000 i - <ESC> > > Vertically enlarge the window about 10 lines. > > That's it. > Unhandled exception at 0x0041226d in gvim.exe: 0xC0000005: Access > violation writing location 0x734b490a.
Crashes on linux as well (GTK2 GUI, 7.0.17). But for crash it is necessary to enlarge the window by at least 5 lines. Enlarging the window by 4 or less lines, and shrinking its size works without problems. Strange, I observed this crash also on another machine (gvim, compiled 8th of May including all the patches till that day, GTK2 GUI) when running locally, but I did not manage to trigger it when running remotely right now. Regards, Peter Cech
