Bug 129633 - silenty dies on extremy long console history
Summary: silenty dies on extremy long console history
Status: RESOLVED DUPLICATE of bug 146483
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 1.6
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-22 12:08 UTC by jernej srebrnič
Modified: 2007-06-09 12:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description jernej srebrnič 2006-06-22 12:08:48 UTC 
Version:           1.6 (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs
OS:                Linux

i develop using JBoss. For developing/debuging i have JBoss set to debug mode to console. It writes a lot. So i set history to "unlimited" and clear the console/history, before executing a specific method.

Time to time i execute a lot of JUnit tests. just interested in the result not in the log, but don't care to change the stings. The log on file (the same as in console) goes to sizes about 1,3G.

after a time the console simply disapers. no error message. 
i think it should check available memory, if just for stopping nicely....
Comment 1 jernej srebrnič 2006-06-22 12:12:34 UTC 
152MB of history and the console is gone :)
Comment 2 Robert Knight 2006-08-07 03:38:14 UTC 
Hello Jernej,

Could you try running Konsole in GDB and try and get a backtrace that way?

If you have history set to unlimited then Konsole stores the history in a file, so there shouldn't be a memory usage issue.

It seems that konsole does however track the size of the Konsole history file using integers - which I would expect to cause problems around the 2GB mark.
Comment 3 Robert Knight 2007-06-09 12:59:57 UTC 
Marking as duplicate of a newer bug which has a backtrace attached.

*** This bug has been marked as a duplicate of 146483 ***