Exited with Status 11 Error keeps coming up.

[slapinheimer]

Before I updated to Boxee alpha 0.9.3935 on my Apple TV everything seemed to work fine. After the update I keep getting the exited with status 11 error.

I am running:
XBMC Atlantis Beta 2
Boxee alpha 0.9.3935
XBMC/Boxee Launcher 0.4
Apple TV 2.1
External USB drive

Any suggestions how to stop the error?

[slapinheimer]

For an active forum I am surprised that nobody has responded to my post regarding the Status 11 error. Has no one else experienced this problem? Any ideas on how to stop Boxee from crashing?

I feel so all alone :(

[marcel]

hi slapinheimer

try and update to the latest version (http://forum.boxee.tv/showthread.php?t=887) are you adding any shares or playing a specific media content when the crash occurred

[Apek]

I get them once in a while as well

[marcel]

@Apek can you describe the flow when they occurred..

[Apek]

Just now, I was looking at a picture (stored in a SMB share), pressed >> and it segfaulted. I got them as well while browsing movies stored in SMB shares.

[davilla]

for crashes, pasting the crashreporter.log to pastebin.com and posting the url here would help.

[paulpangrazzi]

Unfortunately this has happened to me three times tonight as well. Latest build on the ATV. I'll dig for the log file and see if I can post it.

Two times when I used the UI to quit (a long stall and then the exit with msg)
and on it's own just a moment ago when listening to an album on an SMB mounted NAS (with visualization running and Last.FM enabled.)

[mdoggie]

I have had status 10 and status 11 error/exits.

I am updating now to 0.9.3940, frankly I don't know if this is the version I updated to yesterday or not. I do know this - yesterday Hulu worked beautifully, today not at all. The commercials run, then nothing. The progress/play bar keeps accumulating time but no video or sound. Pressing the rewind button gives a message "..player not supported..."

I was able to view other video content from other channels without incident except for the status 10 or 11 errors on exit.

If this is a newer update I'll report back.

[mdoggie]

Ok - running that update must have been a mistake. A restart and then two crashes later, I was able finally to get back into Boxee and navigate to Hulu and still no video.........

The message is actually "player action is currently not supported"

Boxee acts like the video is playing but it is not. This is only with Huku video content so far. CBS, CNN, next new networks, and Comedy Central all stream ok.

[slapinheimer]

I figured out why I was getting the status 11 crash. I had turned on the enable thumbnails option. Once I turned it off the problem went away.

I have an external USB drive attached to my Apple TV. I kept seeing the drive light up and once it reached a certain point into the seek I would get the status 11 error. To fix the problem, I disconnected by external USB drive and rebooted my Apple TV. I was then able to go into the Boxee settings, navigate to Video settings then I found the option to create thumbnails for videos without artwork and unchecked it. I then exited Boxee and reconnected my external USB drive. Opened Boxee back up and BAM! It worked with no Status 11 crash.

Hopefully this fix will preserve the hair follicles of many others experiencing the same problem I had.

The wonderful Boxee folks may wish to see why the thumbnails would be crashing the app. I do have a multitude of ripped raw DVD's on that external drive not sure if the VOB files would be the issue or not.

[detox]

Hey!
That worked for me too.
Thanks

[wildwoodnc]

I ran into this issue as well, and disabling thumbnails corrected the issue.

Thing is, thumbnails worked for a little. By that, I mean that I turned the option on, and I didn't immediately start getting crashes with status 11. IT generated 32 thumbnails which work perfectly fine. Even now, with the option on or off, those 32 thumbnails work fine and xbmc does not crash.

If I scroll to video 33, bam! crash status 11

Not knowing anything about anything I'm going to speculate that this is occurring because of some memory issue either loading or generating thumbnails.

Let me know the location of whatever log files you might need and I'd be glad to upload them.