Child crashes when scrollback buffer is full and new process started which tries to manipulate screen buffer #502
Comments
|
Hi
Windows and ConsoleZ versions are old. Can you provide a crash dump a the child process? Is vim up to date?
This error indicates an error of memory allocation. Perhaps cygwin console layer attempts to allocate a too big memory block. |
|
Everything was installed within the last few weeks, so if it's not latest it's certainly very recent. I'm having trouble get a full crash dump, since the exception gets handled by cygwin so it never propagates to the windows handler. I include some gdb info output and backtrace through. Any gdb output that might be of use I can provide easily. There is no difference in the environments between a consoleZ window and a regular cmd window, other than expected things like ConsoleZBaseDir. Is there anything specific you're interested in? I've experimented more, and found that it's triggered after 26434 lines of scrollback - any less than this and the programs open fine, any more and they error. If I set my scrollback buffer to this size, I can avoid the issue. If I then set it to 26435, I get it again. This is the case independent of window dimensions - I can open a up a window with narrower/shorter geometry, and still get the issues at the same number of lines. It is also independent of the number of characters in each line. I can't reproduce in a cmd.exe tab running under console, so there is something going on where cygwin expects some memory to be alloc'able which console is preventing from happening. I wish I could tell you more, it's a curly one. :-) Any more info you want, let me know, happy to help out any way I can. Backtrace: |
I'm not 100% sure where to file this one - could be console or cygwin. Since I can't reproduce it outside of console I'm going to start here.
Issue is this: once my scrollback buffer is full, the next time I run a program like vim or less, which attempts to manipulate the screen buffer (eg by moving the cursor, clearing content etc), the program does a malloc which fails and the process crashes.
1 [main] vim 15304 C:\Cygwin\bin\vim.exe: *** fatal error - cmalloc would have returned NULLI can reproduce in a cygwin prompt in consolez by generating enough output to fill the buffer, then running vi. I cannot reproduce in a normal (ie cmd) cygwin window with the same process.
My buffer is set to the maximum size of 32766 lines.
Stackdump and diagnostics below. Happy to provide any other info that may useful.
Stack trace:
The text was updated successfully, but these errors were encountered: