Crashing on original iPad under iOS 5.1.1

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is OFF
[flash] is OFF
[url] is OFF
Smilies are ON

Topic review
   

Expand view Topic review: Crashing on original iPad under iOS 5.1.1

Re: Crashing on original iPad under iOS 5.1.1

by Kevin » November 11th, 2012, 11:51 pm

Hello Dave, Thanks for your report!

I have seen something similar and my best guess is that xFeed is using a bunch of memory and the operating system is closing it to get back some of that memory.

But there is good news! There is a new version queued for review which has been running well on an iPad running 5.1.1. If everything goes smoothly, I would expect this update to hit the store before this coming weekend.

Thanks for using xFeed and I hope this works for you!

Crashing on original iPad under iOS 5.1.1

by Dave » November 11th, 2012, 5:15 pm

Ever since the most recent update was pushed, XFeed has been crashing quite regularly on content from certain sites when used on my first-generation iPad. The feeds are downloaded and parsed OK, the article summaries are displayed when selected, but the program crashes when attempting to display the articles themselves. In many cases the articles start to appear, but the program crashes before page rendering is complete.

Examples:

CNN stories... most articles crash and are unviewable.

BBC stories... some but not all crash (running around 50%)

In some cases I've seen, the main article page displays OK, but trying to follow a link from that page to another willl result in a crash.

On several occasions I have used Safari to go to the CNN web site and navigate to one or more of the articles I was unable to view with XFeed, and in each case Safari has not had any problem showing the page or following links.

Possibly, the recent fix for compatibility with iOS 6 might have made things worse on older devices?

Top