petea / sage

A feed reader for Firefox.
http://sagerss.com
27 stars 8 forks source link

Sage blocks Firefox while marking all feed items read #47

Closed petea closed 11 years ago

petea commented 11 years ago

Original author: jubel...@gmail.com (March 08, 2011 11:52:31)

What steps will reproduce the problem?

  1. load a feed (with many items for a bigger effect, http://feeds.jurablogs.com/jurablogs/all?format=xml for example)
  2. click on "Mark all as read"-button ("Alles als gelesen markieren") 3.

What is the expected output? What do you see instead? I expect that the feed is fast marked as read and Firefox stays responsive. Instead Sage blocks Firefox and has a high I/O-load. I can't click on anything. Even then I click the button again, it's doing it again, even though the news items are already marked as read.

What version of Sage are you using? 1.4.9

What version of Firefox are you using? On what operating system? Firefox 4, Windows 7 x64

Please provide any additional information below.

Original issue: http://code.google.com/p/sage/issues/detail?id=48

petea commented 11 years ago

From Peter.A....@gmail.com on March 08, 2011 16:22:56 Does Sage finish marking the items read after a short wait, or does the activity seem to go on forever?

petea commented 11 years ago

From jubel...@gmail.com on March 08, 2011 18:15:23 It finishes after some seconds - for the mentioned feed, my browser needs 50 seconds, if I get my hands off keyboard and mouse and have no other program accessing the hard disk. When clicking around it takes longer, and I get a "not responding" in the titlebar.

Forgot to mention that I sometimes get a script error. Firefox then asks if I want to abort chrome://sage/content/sage.js:651.

petea commented 11 years ago

From Peter.A....@gmail.com on March 15, 2011 03:00:58 Can you tell me which build of Firefox 4 you're using?

petea commented 11 years ago

From Peter.A....@gmail.com on March 25, 2011 07:09:26 Get Satisfaction topic:

http://getsatisfaction.com/sagerss/topics/marking_all_topic_as_read_takes_considerably_longer_after_upgradin_to_f4

petea commented 11 years ago

From Peter.A....@gmail.com on June 16, 2011 04:30:30 I'm unable to reproduce this behavior, but we've gotten a number of reports.

petea commented 11 years ago

From gero.dit...@gmail.com on July 28, 2011 22:38:54 I have a similar behaviour on MacOSX 10.6 using FF4 and 5. After "Mark all as read" FF gets unresponsive EXCEPT that every feed name I mouse over gets wiped out. No change in CPU usage, no script messages. Menus can be dropped down, but commands are not executed. Terminating FF normally using "Activity Monitor" works in one of 20 cases, usually a force quit is needed. FF reports an unexpected quit anyway every time restarted afterwards.

This feed http://www.heise.de/newsticker/heise.rdf is responsible for 95% of my problems and I estimate that every other click on this as Mark Read triggers the problem. Other feeds rarely trigger the problem.

petea commented 11 years ago

From gero.dit...@gmail.com on September 03, 2011 08:35:40 This problem now disappeared in my installation, after I cut back the browsing history from more than 280.000 entries to a mere 1000 using some other addon. Other functions in FF also make it freeze seemingly when operating on 100s of thousands of history entries. In addition, memory consumption overall drops significantly after cutting back the number of history entries.

petea commented 11 years ago

From ivan.ara...@gmail.com on February 17, 2012 20:24:55 I am also experiencing the same problem, except that marking 30 items "read" takes a bout 2-3 seconds and FF (10.0.1) is also blocked.

I know that this is really not a long time, but it is very annoying.

I am experiencing this on laptop with Ubuntu as well as on desktop with Windows 7 (it takes slightly more on laptop, probably due to slower HD, since disk activity is high during this "blocked" period).

BTW, the issue is present since a very long time ago, on various OS-s and FF versions (just never complained before, since the plugin is my favourite :) ).

Regards Ivan

petea commented 11 years ago

From ivan.ara...@gmail.com on April 30, 2012 22:00:05 Update:

linux command "strace -e trace=file -p " shows hundreds of lines like this one during "mark all as read":

open("/dev/urandom", O_RDONLY) = 3

"mark all as unread" also is too long, and hundreds of following pairs are logged:

access("/home/aivan/.mozilla/firefox/i2t2szvw.default/downloads.sqlite-journal", F_OK) = -1 ENOENT (No such file or directory) access("/home/aivan/.mozilla/firefox/i2t2szvw.default/downloads.sqlite-wal", F_OK) = -1 ENOENT (No such file or directory)

Could this be somehow related to the problem?

alanbur commented 11 years ago

Same here - sage is taking an inordinate time to mark feeds read.

petea commented 11 years ago

This should no longer happen with the async history interface.