Bug 334090 - Akregator freezes on exit, no changes saved
Summary: Akregator freezes on exit, no changes saved
Status: RESOLVED UNMAINTAINED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 4.13
Platform: openSUSE Linux
: NOR grave
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-29 16:57 UTC by Benjamin M
Modified: 2017-01-07 22:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin M 2014-04-29 16:57:32 UTC
I cannot exit out of Akregator without it freezing. I then have to kill the process. This not only means my session (and state of feeds) isn't saved, it also frequently duplicates open tabs. The fact that the app doesn't crash, only freezes, means I have no backtrace. 

But not only quitting Akregator, but also exiting out of the aforementioned duplicated tabs will lead to the same behavior. (Other tabs seem to close just fine.) 

The freeze may or may not be related to silverlight and/or java being executed in open content. 

Reproducible: Always

Steps to Reproduce:
1. Start akregator. 
2. Exit out of akregator (including kquitapp and strg+q, or ending a Plasma session with akregator running), or close a tab (s. above). 
3. May be related to tabs containing java or silverlight content. May need web content from certain feeds (this is just a hunch), e.g. open tabs from 99u.com. 
Actual Results:  
The app freezes indefinitely. When killed, akregator later restores none of the changes made.  

Expected Results:  
Akregator should exit and save any changes made during the session. Tabs I want to close should not freeze the app. 

I started akregator through the command line an noticed some messages checking pipelight and java (with no errors), which leads me to believe that the problem could be related to tabs with websites that use any of these technologies. (If you want to try it, the tabs in question are posts from 99u.com)

A note about duplicated tabs: This is a problem I have noticed on crashes for a long time now. Note that this does not happen each time and the duplicating may only occur with a real crash, e.g. when my laptop goes to sleep and needs a reboot as it doesn't wake up. Which has been happening a lot recently.
Comment 1 Benjamin M 2014-04-29 17:01:13 UTC
I forgot to mention 2 points: 
1. Firstly, this bug started occurring in 4.12, so it's not version-related. Secondly, I believe it could have started around the time when I first attempted to exit out of the tab mentioned above, a few days ago, which could confirm this conclusion. 

2. Related bugs could be: https://bugs.kde.org/show_bug.cgi?id=283988 (crash on close tab), or these two older reports on crashes on exit: https://bugs.kde.org/show_bug.cgi?id=301214 , https://bugs.kde.org/show_bug.cgi?id=193780 . Though note that I am describing a freeze, NOT a crash.
Comment 2 Benjamin M 2014-06-19 14:18:44 UTC
An update: I am now experiencing a similar problem with another open tab. I can definitely say that pipelight is not the culprit as akregator still crashes when I disable the silverlight plugin. (The problem I had initially reported went away at one point when akregator simply loaded without the problematic tab open, for reasons I don't know.)

Meanwhile, I have found a workaround for those with tabs that crash akregator. Go to .kde4/share/apps/akregator/ and delete or rename the file "crashed", which saves open tabs at the time of your crash. With the file gone, akregator will load without your troublesome tab.
Comment 3 Denis Kurz 2016-09-24 19:43:09 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:17:03 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.