sparserss consumes almost all the CPU and causes the phone to become unresponsive/freeze

[GoogleCodeExporter]

DO NOT QUOTE COMPLETE LINKS; ISSUE AND COMMENTS WILL BE DELETED OTHERWISE

What steps will reproduce the problem?
1. Wait
2. Phone goes to sleep
3. Randomly phone doesn't respond anymore

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
Version 0.8.3
Android 2.2

Please provide any additional information below.
The phone was totally unresponsive.  I have attached a screenshot of the adb 
shell I used to recover the phone.  I did a top, which identified that 
sparserss was using 97% of the cpu, then I killed sparse rss.  Right after I 
killed sparse rss the phone became responsive.

DO NOT QUOTE COMPLETE LINKS; ISSUE AND COMMENTS WILL BE DELETED OTHERWISE

Original issue reported on code.google.com by niffu...@gmail.com on 1 Mar 2011 at 1:41

[GoogleCodeExporter]

This is a way to large memory consumption.

Please provide additional info such as:
 - how many feeds
 - auto refresh settings
 - phone ram

Thanks!

Original comment by handschuh.stefan on 1 Mar 2011 at 9:45

• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

It is by far the best rss on android I have used.

I have 6 feeds setup.
Auto-refresh is currently disabled for now but when it was setup the refresh 
inteval was 1 hour.  I had the time that entries will be kept set at 1 week 
however I just changed that to 4 days and when I synced today I had to 
force-close sparserss.

I have a Samsung Galaxy S GT-i9000.  I think the phone has about 336MB of RAM.  
I am sitting on about 100MB free at the moment.

Thankyou.

Original comment by niffu...@gmail.com on 2 Mar 2011 at 6:44

[GoogleCodeExporter]

How many entries are there per feed in one week (a rough guess would be enough)?

I have an idea about where the problem is locatet but verifying this will take 
some days.

Original comment by handschuh.stefan on 3 Mar 2011 at 11:26

[GoogleCodeExporter]

The problem didn't happen on the previous version however, the previous version 
I only had three feeds:
1.  A feed from news<dot>com<dot>au
2.  A sister site of the above feed
3.  Slashdot.

I since upgrading to the latest version I have added three more feeds,
4.  The Daily WTF
5.  Techdirt
6.  Arstechnica

I have a feeling that it maybe something to do with 'the daily wtf' feed and a 
problem communicating with that site or maybe an issue with downloading images.

Keeping entries for 4 days, I have this number of entries per feed (as per the 
number listed above)
1.  129
2.  174
3.  55
4.  2
5.  47
6.  46

Feed number 4 I have noticed the majority of time doesn't have any new entries 
to download.

Let me know if I can help in any other way (java is pretty much the only 
language I can't program in).

Original comment by niffu...@gmail.com on 4 Mar 2011 at 9:52

[GoogleCodeExporter]

Thanks for the detailed information.
Just to be sure: you have enabled the option to download the images?

There was an issue with the connections that are opened, but in the attached 
version, they are all closed manually.
Please let me know, if there is any improvement.

ps: the attached package is compiled from revision 101

Original comment by handschuh.stefan on 5 Mar 2011 at 8:05

[GoogleCodeExporter]

Originally I had enabled downloading pictures, I recently disabled downloading 
pictures to see if that helped.

I will enable downloading pictures to test this new version out.

Original comment by niffu...@gmail.com on 7 Mar 2011 at 1:43

[GoogleCodeExporter]

I have run it now since march the 5th and so far I have not lost control of the 
phone when I manually update the feeds.  

I took the following top statistics, hopefully they give you some usefull 
information.

I used the following command:
    C:\samsung>adb shell "top|grep -i rss"

Before running a manual refresh of feeds:
  PID CPU% S  #THR     VSS     RSS PCY UID      Name
12730   0% S     6 221592K  22360K  fg app_124  de.shandschuh.sparserss

After I Clicked on refresh
12730   0% S     7 224456K  22756K  fg app_124  de.shandschuh.sparserss
12730   1% S     7 224320K  22816K  fg app_124  de.shandschuh.sparserss
12730   2% S     7 225292K  24716K  fg app_124  de.shandschuh.sparserss
12730   6% S     7 225480K  25188K  fg app_124  de.shandschuh.sparserss
12730  13% S     7 225476K  25076K  fg app_124  de.shandschuh.sparserss
12730  22% S     7 225476K  25480K  fg app_124  de.shandschuh.sparserss
12730   0% S     7 225452K  25172K  fg app_124  de.shandschuh.sparserss
12730   5% S     7 225452K  25324K  fg app_124  de.shandschuh.sparserss
12730  19% S     7 225520K  25352K  fg app_124  de.shandschuh.sparserss
12730  25% S     8 226544K  25560K  fg app_124  de.shandschuh.sparserss
12730  26% S     8 226544K  25588K  fg app_124  de.shandschuh.sparserss
12730  17% S     8 226636K  25688K  fg app_124  de.shandschuh.sparserss
12730   9% S     8 226636K  25692K  fg app_124  de.shandschuh.sparserss
12730  10% S     8 226628K  25364K  fg app_124  de.shandschuh.sparserss
12730  10% S     7 223544K  25356K  fg app_124  de.shandschuh.sparserss
12730   0% S     7 223544K  25356K  fg app_124  de.shandschuh.sparserss

After all the feeds were updated:
12730   0% S     7 223544K  25356K  fg app_124  de.shandschuh.sparserss

Note that the intervals that I took were not at any fixed interval.

Is there anything else can I do for you to confirm that its fixed the problem?

Original comment by niffu...@gmail.com on 11 Mar 2011 at 4:40

[GoogleCodeExporter]

I had to connect the usb cable and do a kill -9 to sparserss today.  Then the 
phone rebooted.

Original comment by niffu...@gmail.com on 31 Mar 2011 at 2:14

[GoogleCodeExporter]

Sorry for the delay.

Does the attached version (compiled from the current sources) fix the problem?

Original comment by handschuh.stefan on 1 Apr 2011 at 4:29

[GoogleCodeExporter]

A fix should be released in version 0.8.5.

Original comment by handschuh.stefan on 1 Apr 2011 at 4:58

[GoogleCodeExporter]

This is fixed in the official 0.8.5 release.

Original comment by handschuh.stefan on 3 Apr 2011 at 2:46

• Changed state: Fixed