Re: GVIM 7.3 can not start up due to BadAlloc

Thanks for replying. But I don't think it is because of large file
sizes. I can open the same file using 7.1 and the files are by no
means large.
I could start the 7.3 gvim a few times but 90% of the time it gave me
the error message. I did notice the interface of the 7.3 gui is
different from what 7.1 invoked.

On Apr 6, 11:10 pm, Tony Mechelynck <antoine.mechely...@gmail.com>
wrote:
> On 07/04/11 04:39, Jerry wrote:

>
> > Hello, I have just installed vim 7.3. When I try to start gvim, I got
> > the following error message:
>
> > The program 'gvim' received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'BadAlloc (insufficient resources for operation)'.
> >    (Details: serial 503 error_code 11 request_code 53 minor_code 0)
> >    (Note to programmers: normally, X errors are reported
> > asynchronously;
> >     that is, you will receive the error a while after causing it.
> >     To debug your program, run it with the --sync command line
> >     option to change this behavior. You can then get a meaningful
> >     backtrace from your debugger if you break on the gdk_x_error()
> > function.)
>
> > Does anybody know what is happening here? I would appreciate any
> > input. BTW, I am running vim on Solaris.
>
> > Thanks, everybody.
>
> Maybe trying to edit a very big file on a system with little memory? If
> the file is larger than the sum of your free RAM and free swap, there's
> no way Vim can edit it. If it's "almost" as large, it won't be easy. And
> in general, of course, virtual memory is much slower than actual RAM.
>
> Best regards,
> Tony.
> --
> If you don't care where you are, then you ain't lost.

--
You received this message from the "vim_use" 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