search

mpinegar / understudy

Automatically exported from code.google.com/p/understudy
GNU Lesser General Public License v3.0
0 stars 0 forks source link

crash while netflix episode information is loading #144

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
I'm a first time Understudy 0.81 user and every time I select Add Feed ->
NetFlix, it crashes Front Row.  I was able to add a HuLu feed without a
problem.

What is the expected output or result?
Not crashing?

What do you see instead?
Exits to the Finder.

Please provide any additional information below, including any relevant
URLs.
My specs are Mac Mini 2.26GHz, 2GB RAM, 10.6.2.  I'm a SW developer so if
you need me to try something, please ask.

(Before submitting this issue, please ensure that you will be notified of
updates by adding yourself to the CC field or by staring the issue and
configuring your profile setting.)

Original issue reported on code.google.com by scott%fought.net@gtempaccount.com on 15 Feb 2010 at 9:51

GoogleCodeExporter commented 8 years ago 
If there is a crash report generated in ~/Library/Logs/CrashReported/ (either 
for 
FrontRow or NetflixPlayer), please attach it.

Original comment by kirk.kel...@rochester.edu on 26 Feb 2010 at 4:34

GoogleCodeExporter commented 8 years ago 
I am experiencing a similar issue.

I successfully added my Netflix Instant Queue (meaning the item was added to 
Understudy, and Front Row still 
functions normally aside from the issue noted here), but when attempting to 
load/navigate my Netflix Instant 
Queue, as the graphic loads for the first item in the queue, Front Row crashes.

See attached crash report.

Original comment by shelter....@gmail.com on 2 Mar 2010 at 4:05

Attachments:

GoogleCodeExporter commented 8 years ago 
Allowing FrontRow to sit for a period of time on the main Understudy window, 
prior to entering the Netflix 
Instant Queue, yields a different - and possibly more informative - exception 
type on entering the queue.

See attached crash report.

Original comment by shelter....@gmail.com on 2 Mar 2010 at 4:21

Attachments:

GoogleCodeExporter commented 8 years ago 
The current work-around (at least on this computer) appears to be quickly 
scrolling downward through the 
queue, as soon as the queue is entered. Waiting ~30-45 seconds then allows 
playback from all items within the 
queue, without crashing.

Original comment by shelter....@gmail.com on 2 Mar 2010 at 5:05

GoogleCodeExporter commented 8 years ago 
Further testing revealed that by uninstalling 0.8.1 and installing 0.7 in its 
place,
the crashing issue when entering the queue simply wasn't present. 0.7 does not 
have
the enhanced features of 0.8.1, so I have gone back to the latest release... 
but it
would be nice if the stability of 0.7 (at least for the Netflix Instant Queue, 
which
is the only aspect of understudy that I have tested) could be restored to 0.8.1.

I probably should have mentioned earlier that today was my first exposure to
understudy, so if anything that I mention in my blind
hammer-away-until-something-works approach is already common knowledge, please
forgive the redundancy.

Original comment by shelter....@gmail.com on 2 Mar 2010 at 10:33

GoogleCodeExporter commented 8 years ago 
I get the crash upon entering Netflix Q. I can send a crash dump if you would 
like one.

Original comment by slgarw...@gmail.com on 18 Mar 2010 at 2:01

GoogleCodeExporter commented 8 years ago 
I've seen crashes similar to the one attached to comment 3 (some object gets an 
invalidate message and can't handle it). I've been holding off releasing an 
update 
until I can fix this, but since Netflix isn't working at all for many people 
I'm going again. Suffice to say that release 0.8.2 doesn't fix this. The issue 
doesn't exist in 
version 0.7, but it would be helpful if someone could check release 0.8.0 for 
me.

(this was originally a crash during when adding a netflix feed, but it's been 
hijacked. If that problem still persists for anyone, please create a new issue 
for it)

Original comment by kirk.kel...@rochester.edu on 19 Mar 2010 at 1:26

GoogleCodeExporter commented 8 years ago 
I believe release 0.8.3 fixes this issue

Original comment by kirk.kel...@rochester.edu on 21 Mar 2010 at 1:59