[Debugger] Exhibits inconsistent behavior & doesn't save a crash report
|Reported by:||waddlesplash||Owned by:||anevilyak|
Running rm through "stdbuf" invariably crashes it:
stdbuf -o L rm -rf /some/directory/
/some/directory doesn't even need to exist, that's optional.)
Attempting to click "save report" in the resulting crash dialog does create a file on Desktop with either:
- first few lines of the stacktrace, but there's nothing beyond that and Debugger just starts chewing up lots and lots of memory.
- all the way to the start of the "Semaphores" group (but nothing in it), with Debugger sitting at a constant (low) memory usage using no CPU.
I can't figure out what's causing this. The system isn't under heavy load, has plenty of ports free (only 118 used), and it always occurs, even after a reboot.
x86_64 (does not occur on x86_gcc2), hrev49425 in VirtualBox. It would be nice to get a solution to this soon, as it's blocking me working on the Kitchen more, as I'm hesitant to use a workaround on "rm" until I know what the bug is...