Tallefer / prssr

Automatically exported from code.google.com/p/prssr
GNU General Public License v2.0
0 stars 0 forks source link

I can only launch pRSS reader once #130

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
I load pRSS Reader and I can load it, import my opml and it seems to work
fine.  I close it and then I cannot load it again.  Even after a soft
reset.  The only thing that will correct this is a hard reset.  It happens
every time after a hard reset in this same order.   

What is the expected output? What do you see instead?
Won't launch

What version of the product are you using? On what operating system?
1.4.4 on WM 6.1 on a HTC Fuze

Please provide any additional information below.

Original issue reported on code.google.com by jaf...@gmail.com on 27 Dec 2008 at 4:49

GoogleCodeExporter commented 9 years ago

Original comment by and...@gmail.com on 27 Dec 2008 at 9:24

GoogleCodeExporter commented 9 years ago
Ok I have more info on this.  I did a hard reset and installed only pRSS 
reader. I 
could install and open pRSSr.  I install my opml and all is well.  I can open 
and 
close pRSSr as much as I want.  When I try to update all feeds I get an error 
halfway  
through.  It says Out of Memory.  I click OK and the update finishes fine.  I 
can 
navigate and read my feeds and all is well.  When I close pRSSr it seems fine 
but I 
cannot reopen it from here.  I  have to uninstall it and reinstall it to get it 
to 
open again.  If I do reinstall it and open it none of my feeds are there (which 
I 
expect because I select not to save settings).  I can go to manage feeds and 
import 
my opml again.  When I check close I get the same Out of Memory error again.  I 
click  
ok and none of my feed are there.  I click on manage my feeds again and they 
are 
there.  I click close and they show up.  I can then update my feeds and read 
them.  
If I exit now though I can not reopen pRSSr.  It seems to have to do with the 
out of 
memory error.  what ever causes that is keeping me from reopening the 
application.

Hope this helps.

Original comment by jaf...@gmail.com on 28 Dec 2008 at 12:41

GoogleCodeExporter commented 9 years ago
If you are getting out of memory condition, I wonder:
1) how much memory do you have (in total)?
2) how much is usually free?
3) how many feeds are you subscribed to? (Or send you OPML file here)

Original comment by and...@gmail.com on 28 Dec 2008 at 9:51

GoogleCodeExporter commented 9 years ago
I have trouble believing that memory is actually a problem.  I have tried it on 
four 
different ROM's, all optimized for memory.  I have attached screen shots of the 
latest two.

I have also used this exact same opml file in 4 different RSS readers 
successfully 
(Egress, Beyondpod, rSS Hub by illumsoft, and freerange reader).  I am sort of 
an RSS 
junkie.  It is always the first thing I load after a hard reset and it never 
leaves 
the MRU.  

From what I have seen I like the functionality of yours the best.  I hope we 
can work 
this out because IO am anxious to use it.  Let me know if there is anything 
else that  
I can do.

Original comment by jaf...@gmail.com on 28 Dec 2008 at 4:30

Attachments:

GoogleCodeExporter commented 9 years ago
If you do the fresh update (the first one) and immediatelly quit the prssr, it 
starts
to save the data on the background. At that moment, you can not reopen it 
(since it
is already running and WinMo allows only one instance of each application).

But if you start to read after the update, the feeds are also saved on the
background, so you should be able to reopen prssr after quit (of course, all the
feeds has to be saved - then the quit is fast).

What I am confused about, the you cannot opne the prssr after the soft reset.

And of you are getting out of memory condition, then my question about the 
momoery on
your device are more than relevant. There is another issue opened raletd to out 
of
memory condition, so it might be related.

OPML file: It looks reasonable in terms of size. I saw lists with hundreds of
subscriptions - that would explain a lot in terms of your issue. I'll try your 
file
on my device, to see what it does. Will report back here.

There is one more thing: How did you set the archiving options? How many items 
do you
keep in the cache? The more items, the more memory consumptions, the longer 
time to
save feeds -> longer time when you cannot open prssr (see above). 

The last thing: Did you also try the original ROM for your device?

Original comment by and...@gmail.com on 28 Dec 2008 at 6:27

GoogleCodeExporter commented 9 years ago
I did not try it on the stock rom.  I can if you think that it will help but I 
imagine that there is not a problem.  I found your app on xda under a Fuze 
thread so 
I bet that it works and it is just something that this ROM is  doing.  I posted 
a 
question in the ROM  thread but I have not heard anything.  

Like I said I doubt it is the opml since it works in other rss readers on this 
phone.    
I think that this one only has 30 or so feeds.

I did not change the default archiving settings.  I think that they were set to 
50 
when it was installed.  Let me know if you need any more information.

Thanks
cj

Original comment by jaf...@gmail.com on 29 Dec 2008 at 2:29

GoogleCodeExporter commented 9 years ago
Ok I found the problem.  It is not the ROM or the phone.  It is one specific 
feed.  I 
asked NATF the chef that cooked the ROM I am using to try pRSS reader out and 
he did 
not have any problems.  As I stated before I have tried it on a fresh hard 
reset with 
no other apps installed and it did not work.  So that means that it was one of 
two 
things, my phone or one of the feeds in my opml.

So here is what I did. I hard reset.  Installed pRSSr and imported my feeds  
one 
category at a time.  They all imported fine which is what I expected.  I then 
updated 
them one at a time and all but one updated with out an error.  The one that 
kicked 
and error did seem to update but I got the out of memory error.  By this time I 
had 
most of my feeds updated and 509 unread articles so just to be sure I hard 
reset 
again.  Then I loaded pRSSr and just the one feed.  I hit update and sure 
enough Out 
of Memory.  there must be something in this one feed that is causing the 
problem. 

Here is the URL:  http://feeds.feedburner.com/FuzeMobility

It is one of my favorites so hopefully you can figure out what is causing the 
problem.  It is on feedburner (as are several other feeds that I read) so I 
can't 
imagine that it has anything crazy in the formatting.

Thanks again for any help.

cj

Original comment by jaf...@gmail.com on 29 Dec 2008 at 9:49

GoogleCodeExporter commented 9 years ago
Update.  I may actually be one specific post.  Assuming that they are 
downloaded in 
order.  

I always get this post:  http://www.fuzemobility.com/?p=1438

but never this one:  http://www.fuzemobility.com/?p=1444

thought it might help...

Original comment by jaf...@gmail.com on 29 Dec 2008 at 10:01

GoogleCodeExporter commented 9 years ago
I am experiencing the same issue on my Fuze with version 1.4.4. I also have
FuzeMobility in my list of feeds.

Original comment by sean.a.d...@gmail.com on 31 Dec 2008 at 9:31

GoogleCodeExporter commented 9 years ago
I confirm the issue is with the fuzemobility feed. I tested further today by 
removing
the feed from my subscription list. I could open and close pRSS without issue. 
Once I
add fuzemobility I get the out of memory error and the application crashes 
every time
I try to reopen. 

I tried adding tiltmobility.com's feed (sister site of fuzemobility and also 
uses
feedburner). I can add this feed just fine so it definitely is down to 
something in
the fuzemobility.com feed itself.

Original comment by sean.a.d...@gmail.com on 1 Jan 2009 at 8:43

GoogleCodeExporter commented 9 years ago
Don't believe I have the same feed in my list, but the issues sound exactly the 
same - and most frustrating, as no RSS for PDA seems to quite match this for 
features etc.

However, believe devlopment on this is now closed - but would like to believe a 
final comment from the maker of this otherwise great appmight appear ..! ;-)

Original comment by lilacti...@gmail.com on 1 Mar 2009 at 12:48