Summary: | Crash: Loading previous manually stored session crashes with SIGABRT | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | gmud <geroxp> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | edulix |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | incomplete session file results in crash with above bt |
Description
gmud
2008-09-23 11:58:02 UTC
I use saved sessions all the time and they work for me, perhaps it's a special webpage or saved configuration that is failing to you? You could perhaps attach the session if you don't mind so that we can try to reproduce. The session is a directory at $KDEHOME/share/apps/konqueror/sessions/<session name> (which is usually set to ~/.kde4). Created attachment 27526 [details]
incomplete session file results in crash with above bt
Ok, so I looked into this directory and there are two files. One has all the session information and one is somehow not complete. If I delete the incomplete one, session restore works perfectly. I'll attach the incomplete one. It has Tabs0_activeChildIndex=-1 set, maybe this is the problem?
Each file inside your session directory represents a different konqueror process. I wonder how a konqueror process ended up writting a config file like the one you attached uhm. Perhaps you know how to reproduce that? I have crashes of konqueror a couple of times daily. Maybe I saved the session and then closed konqueror and it crashed? I can't remember... I will try to reproduce. However, konqueror should not crash when having to read an incomplete or broken session file. SVN commit 984427 by edulix: Don't crash if can't et current index, just give a warning instead CCMAIL:faure@kde.org BUG:171500 M +8 -4 konqviewmanager.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=984427 |