Red Hat Bugzilla – Bug 68144
mc eats all my memory and then seg faults when trying to edit a file
Last modified: 2007-04-18 12:43:55 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513
Description of problem:
When trying to edit a file mc crashes either instantly with a seg fault or first
eats all my memory and then seg faults.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start mc and try to edit a file
This also happens on my computer.
("mcedit foo.bar" when in X makes the system swap like crazy
and after a while this process gets killed.
Running "mcedit in a virtual console (like /dev/tty1)
immediately gives a Segmentation fault).
Reproduced, mcedit foo.bar segmentation faults.
Maybe a gpm or slang/curses/utf-8 thing?
Maybe. It appears to happen with all the latest versions of slang/newt/etc.,
which should have most of the problems fixed.
Still broken in mc-4.5.55-10
mc in limbo beta2 still crashes when trying to edit a file.
This is maybe not related, but when trying to copy a file with mc (mc-4.5.55-7),
it will segfault. When to upgrade to mc-4.5.55-11 from Raw Hide it is OK.
Confirm Midnight Commander crash in Limbo 7.3.93.
After starting "mcedit <somefile>" the virtual memory grows from 30 MB to
100+ MB, the system gets *really* slow and unresponsive for a couple of
minutes, then the Midnight Commander process gets killed).
This is in a GNOME 2 terminal window.
*** Bug 70257 has been marked as a duplicate of this bug. ***
Doesn't happen in GNOME2 Terminal only. Even on the real console mcedit dies
trying to open a file.
Even an ordinary HelloWorld.c forces mcedit to consume all available RAM until
Linux starts swapping till all swap is full and then the kernel kills mcedit.
see bug #71039
*** This bug has been marked as a duplicate of 66794 ***