[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 169851] KJS crash while using Horde bugtracker
From:       Eduardo Robles Elvira <edulix () gmail ! com>
Date:       2008-08-26 20:23:57
Message-ID: 20080826202357.6CB536683 () immanuel ! kde ! org
[Download RAW message or body]

http://bugs.kde.org/show_bug.cgi?id=169851


Eduardo Robles Elvira edulix gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |edulix@gmail.com




--- Comment #4 from Eduardo Robles Elvira <edulix gmail com>  2008-08-26 22:23:54 ---
(In reply to comment #3)
> Is there a good reason why I was able to crash it every time once it resumed
> the "broken" session? I guess the konqueror session saves URL, window size and
> other stuff in there. Where does this get saved to? Maybe the session data gets
> corrupted and that's why I was able to trigger it over and over again once it
> happens.
> 

Well the reason is konqueror saves everything it can, even the buffer (which is
normally the largest part), for every historyitems (back &forward arrows for
each konq view). I plan to make the crash session manager smarter smarter for
4.2 so that it can detect  when a session is crashy and try to somehow deal
with it but it's not done yet.

You can see the saved session as files (one per konqueror process) inside
~/.kde/share/apps/konqueror/autosave.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]