Bug 90085 - Problems with aborting fetch transactions
Summary: Problems with aborting fetch transactions
Status: RESOLVED WORKSFORME
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: cvs
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-23 11:52 UTC by Frank Osterfeld
Modified: 2004-11-03 23:17 UTC (History)
2 users (show)

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 Frank Osterfeld 2004-09-23 11:52:43 UTC
Stephan discovered bugs in the fetch transaction. I just dump what he told me 
on IRC: 
 
- hello, just discovered another bug with non-responding site/no system tray 
update :-| 
 
- Steps to reproduce: Have a non-responding site in your list (like atm 
http://www.gnomedesktop.org/backend.php). 
 
- Do a "Fetch All", when progress bar hangs at 96% because of this "Stop" 
 
- Start a new "Fetch All" or wait for a periodic fetch to happen. It polls all 
sites (of course waiting for the non-responding site to time-out), the progress 
bar disappears (!), but "Stop" is not disabled, the "Fetch" buttons enabled and 
the unread system tray counter is not updated anymore. 
 
- Oh, if you then press "Stop" aKregator crashs. 
 
[KCrash handler] 
#7  0x416e199b in RSS::Loader::abort () 
from /opt/kde-head/lib/kde3/libakregatorpart.so.1 
#8  0x416b2c79 in Akregator::Feed::abortFetch () 
from /opt/kde-head/lib/kde3/libakregatorpart.so.1 
#9  0x416b6419 in Akregator::FetchTransaction::stop () 
 
- Everything works repeatedly fine if you never press "Stop". 
 
- It seems that pressing "Stop" at any time of fetching confuses aKregator: 
doesn't ungray icons, next poll stops at some random position (40%), still 
active "Stop" leads to crash :-(
Comment 1 omschaub 2004-09-24 21:40:41 UTC
This is EXACTLY what is happening on my system too.. to the letter!

And if you ps aux | grep akregator .. there are always 10-20 threads open for akregator.  Like these:

xxxx     14401  0.0  1.4 72348 14984 ?       S    07:48   0:00 kdeinit: kio_http http /tmp/ksocket-xxxx/klauncher3eW7Db.slave-socket /tmp/ksocket-xxxx/akregatorzQDyMb.slave-socket
xxxx      2452  0.0  1.4 72348 14628 ?       S    10:08   0:00 kdeinit: kio_http http /tmp/ksocket-xxxx/klauncher3eW7Db.slave-socket /tmp/ksocket-xxxx/akregatortZGoDa.slave-socket
xxxx      2457  0.0  1.4 72348 14632 ?       S    10:08   0:00 kdeinit: kio_http http /tmp/ksocket-xxxx/klauncher3eW7Db.slave-socket /tmp/ksocket-xxxx/akregatortZGoDa.slave-socket


The only way to get akregator out of this crashed situation is to kill all the open threads (open even after akregator is closed) and restart akregator.  Alas.. a major bug, but it is tolerable since akregator is the BEST rss reader out there!
Comment 2 Frank Osterfeld 2004-10-31 22:39:54 UTC
I can't reproduce this with current CVS anymore. Could you check (if you use CVS) if these problems still occur? 
Comment 3 omschaub 2004-11-01 01:51:20 UTC
Unfortunately, Gentoo just has the b7 and it is still there in that version.. I will wait until another beta is posted and get back to you on how it performs on my systsm.
Comment 4 Stephan Binner 2004-11-03 23:17:58 UTC
Seems to work now.