Bug 7835 (int-139806)

Summary:	High CPU usage of osso_rss_feed_reader; huge searchentries file
Product:	[Maemo Official Applications] RSS feed reader	Reporter:	Peter Oliver <bugs.maemo.org>
Component:	General	Assignee:	unassigned <nobody>
Status:	UNCONFIRMED	QA Contact:	rss-feed-reader-bugs
Severity:	major
Priority:	Unspecified	CC:	andre_klapper, dev2, eero.tamminen, maemo, magnet.elie, michelm.jacques, simon.hall
Version:	5.0:(10.2010.19-1)	Keywords:	use-time
Target Milestone:	---
Hardware:	N900
OS:	Maemo

Description Peter Oliver (reporter) 2010-01-12 01:44:37 UTC

Process osso_rss_feed_reader consumes all available CPU and depletes the
battery.  In this example it is process 2973:

/home/user # ps -ef | grep rss
 2972 user      3936 S    /usr/bin/osso_rss_feed_reader --iconify 
 2973 user     24928 R    /usr/bin/osso_rss_feed_reader                        
/home/user # strace -p 2973
Process 2973 attached - interrupt to quit
read(13, "", 4096)                      = 0
read(13, "", 4096)                      = 0
read(13, "", 4096)                      = 0
...
read(13, "", 4096)                      = 0
read(13, "", 4096)                      = 0
read(13, "", 4096)                      = 0
^CProcess 2973 detached
/home/user # lsof -p 2973 -a -d 13
COMMAND    PID USER   FD   TYPE DEVICE      SIZE  NODE NAME
osso_rss_ 2973 user   13r   REG  179,2 183070720 24585
/home/user/.osso_rss_feed_reader/searchentries
/home/user # ls -l /home/user/.osso_rss_feed_reader/searchentries
-rw-r--r--    1 user     users   183070720 Jan 11 15:22
/home/user/.osso_rss_feed_reader/searchentries
/home/user # od /home/user/.osso_rss_feed_reader/searchentries
0000000 066145 067141 000000 000000 000000 000000 000000 000000
0000020 000000 000000 000000 000000 000000 000000 000000 000000
*
1272270000

I'm not using the RSS feeder application or applet.  If I try to start the RSS
application, it crashes.  If I kill the process or reboot the device, the
problem returns later.

I have now renamed .osso_rss_feed_reader and will see if that cures the issue.

Comment 1 Andre Klapper maemo.org

2010-01-15 15:12:48 UTC

Does this still happen in 2.2009.51-1?

Comment 2 Peter Oliver (reporter) 2010-01-18 22:04:50 UTC

Hard to say.  It copes just as badly if I replace the large searchentries file.
 However, I'm not sure what caused that file to be created in the first place:
after removing it, it hasn't yet returned.

Comment 3 simon.hall 2010-01-26 16:40:16 UTC

I also get this error on start up. Killing the process causing the OS to
re-start, this defect renders the handset unusable, reduces battery life to a
few hours.

Comment 4 Andre Klapper maemo.org

2010-02-09 23:38:41 UTC

Simon: Can you provide the same output as Peter?
You are running 2.2009.51-1 I assume?

Comment 5 Chris Pitchford 2010-02-10 15:10:20 UTC

I've just helped a user at discussions.nokia.com with either this or a similar
problem. The searchentries file had swollen to 1.5gig.. He removed the file and
the RSS reader and widget both seem to be behaving themselves now.

He's been running 2.2009.51-003 since a few days after its release. The file
problem happened on the 4th Feb, so some time after the upgrade. It was working
normally prior to that.

Comment 6 Andre Klapper maemo.org

2010-02-10 15:13:34 UTC

(In reply to comment #5)
> I've just helped a user at discussions.nokia.com

Direct URL welcome :)

Comment 7 Chris Pitchford 2010-02-10 15:15:51 UTC

(In reply to comment #6)
> (In reply to comment #5)
> > I've just helped a user at discussions.nokia.com
> 
> Direct URL welcome :)
> 

face palm.. sorry.. ctrl + V.. paste properly, now :)

http://discussions.europe.nokia.com/t5/Maemo-Devices/Mail-for-exchange-user-storage-full-low-memory-for-installable/td-p/625719/jump-to/first-unread-message

Comment 8 Andre Klapper maemo.org

2010-03-01 21:18:50 UTC

Peter: Ypu still see the same problem in 3.2010.02-8?

Comment 9 Eero Tamminen nokia

2010-03-23 16:35:28 UTC

This sounds like file system corruption (which shouldn't happen on Ext-3).  Or
if that file is SQLite database, the database file corruption (which can
happen).

Comment 10 Christian Sarrasin 2010-06-09 01:26:31 UTC

FWIW just had that very same problem today for the first time (running PR1.2).
My osso_rss_feed_reader went balistic, eating up all cpu.  I followed the
advice and deleted 'searchentries' which does indeed solve the problem but also
looses my rss configuration as a side-effect; not too pretty.

I have been running the rss desktop widget for over 6 months, with a handful of
(maybe 6) subscriptions and used it almost on a daily basis but never noticed
this before.  Once the problem started occuring, the widget would stay blank
with "no posts" with no way to getting it to refresh properly.  My
"searchentries" file had grown to 5.1MB by the time I rm'ed it.

Here is perhaps the only new piece of info regarding this: this started
happening just after I had my SIM card exchanged by my carrier (Vodafone)
because the old one was faulty.  I don't necessarily think that the SIM card in
itself caused this but one side-effect tha had was to reset some of my settings
(and presented me with a aome sort pretty cut down regional/time settings
Wizard after I first booted with the new card).  One thing I noticed this had
reset in particular was the "auto-connect to the Internet" setting.  Maybe this
is  related?

Comment 11 Michel Jacques 2010-08-27 17:24:35 UTC

I have the same problem although I can't strace the process.  But my load are
all over 1.15 (which is a lot for an handheld)

-I have a swollen searchentries at 160 MB for now.
-I recenlty begin to reuse the applet I stop using this winter.  I didn't
detect any problem at that time and this is not why I stop using it.
-Can't start RSS reader (it crash)
-Deleting searchentrie does not mitigate anything.  I still have my process at
98%.  searchentrie was not recreated by the process
-Killing the process (kill -9) seem to give me a break.  My phone is at room
temprature, the load is 0.01 and no sign of this osso_rss_feed_reader process.
   I can now start RSS Reader and see my feed.  No sign of the gangster.

The things i changed recently:
- Program a cron job to synchonize file on a server over Wifi.  This script
uses ssh and scp and run every 10 mins.  (I don't believe this has anything do
to with the problem at hand but I mention it nonetheless)
- set wifi config to connect automatically when a known network is available. 
This change relate to Christian Sarrasin's post.

NOKIA N900
MAEMO 5
VERSION: 10.2010.19-1.002

Comment 12 elie-7 2010-09-25 15:54:12 UTC

guys i'm a noob and i'm having this bug, how can i fix it ???????