On Tue, October 12, 2010 6:58 am, Benjamin R. Haskell wrote: > Also fine here, using Gvim 7.3.14 under Gentoo Linux, after bumping the > number of iterations to 10,000. > > But, running the test under Win7 showed the bug. There, under Vim 7.3e > beta, after approximately 2500 iterations, I started seeing: > > E235: Unknown font: Fixedsys:h9:cDEFAULT
I see that on Windows XP with Vim 7.2.284 after approximately 20000 iterations. But what is really weird is, that the whole gui is broken afterwards. The window is not redrawn correctly afterwards and when typing the letters appear in the root window (e.g. it looks like I am typing on the Desktop of Windows itsself) and all different artifacts are drawn on the screen. Even after quitting vim, I still see some artifacts. Very weird. > > So, maybe some kind of font structure is getting allocated and not freed > when unused? (Possibly because there's no way to know it's unused?) > > Either way, this script triggers the same error, but I'm not sure it's > the whole cause: > > ==> minimal.highlight.bug.vim <== > for i in range(50000) > highlight Normal guifg=#ffffff > endfor That triggers the same bug, but does not error the message. > ================================= > > Doesn't look nearly as dramatic. Adding the redraw at the end of the > loop is what causes the flashes. > > Run via: > > gvim.exe -u NONE -N +'syntax on' +'source %' > /path/to/minimal.highlight.bug.vim > > Or, if you want to see the message (since the GUI becomes unreadable > after the font goes missing -- though it seems to gradually return to > near-normal): > > gvim.exe -u NONE -N +'syntax on' +'source %' +'redir! > ~/vim.error.msg' > +'silent! messages' +'redir END' +'q!' /path/to/minimal.highlight.bug.vim That triggers the same but, but I don't see the error message in the redirected file. regards, Christian -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
