# "Crash Report Submitted" loop

**URL:** <https://forums.plex.tv/t/crash-report-submitted-loop/100081>\
**Category:** Apps & Creations\
**Created:** [April 16, 2015, 7:02pm UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081 "2015-04-16T19:02:55Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nibb31](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/nibb31/32/12439_2.png) [@Nibb31](https://forums.plex.tv/u/Nibb31)\
**Post date:** [April 16, 2015, 7:02pm UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081/1 "2015-04-16T19:02:55Z")

</div>

For some reason, my Rasplex crashed (RPI2 on 0.5.1) and when I restart, it gets stuck constantly displaying "Crash Report Submitted" with a number. I can only click OK, the window goes away, then comes up again with an incremented number.

&nbsp;

It started somewhere about 50050 and I've been patiently clicking OK until it's now at 50230, with no sign of it ever ending. For all I know it might have 10000 more crash reports to submit...

&nbsp;

How can I get out of this loop?

---

<div class="post-metadata">

**Author:** ![AltonV](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/altonv/32/84340_2.png) [@AltonV](https://forums.plex.tv/u/AltonV)\
**Post date:** [April 16, 2015, 7:05pm UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081/2 "2015-04-16T19:05:25Z")

</div>

Reinstalling rasplex?

---

<div class="post-metadata">

**Author:** ![Nibb31](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/nibb31/32/12439_2.png) [@Nibb31](https://forums.plex.tv/u/Nibb31)\
**Post date:** [April 16, 2015, 7:14pm UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081/3 "2015-04-16T19:14:25Z")

</div>

That would be a last resort solution. I'm not keen on going through the hassle of setting everything up again, especially as I was actually waiting for 0.6 "any day now", but it looks like it might be the only way to get unstuck.

A crash is bad enough. Forcing the user to submit hundreds of crash reports afterwards is a stupid design decision.

---

<div class="post-metadata">

**Author:** ![dlanor](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dlanor/32/4522_2.png) [@dlanor](https://forums.plex.tv/u/dlanor)\
**Post date:** [April 16, 2015, 8:44pm UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081/4 "2015-04-16T20:44:06Z")

</div>

> That would be a last resort solution. I'm not keen on going through the hassle of setting everything up again, especially as I was actually waiting for 0.6 "any day now", but it looks like it might be the only way to get unstuck.
> 
> A crash is bad enough. Forcing the user to submit hundreds of crash reports afterwards is a stupid design decision.

The behaviour you see, of repeated crash report demands, is obviously NOT something anyone decided to implement. (Only the ability to report a crash is.)

What you see is a result of some error which really is causing this crashing to occur repeatedly. (Multiple crashes are NOT buffered for future report requests.)

While the only clearly visible option is "OK", you may also be able to dismiss that dialog box by pressing 'Escape' (assuming you have a USB keyboard), or possibly what other remote button you normally use to 'back out of' or dismiss submenus and dialog boxes. If that works I recommend doing a "Shut Down" or "Restart" command next, so as to try for a clean boot. Another keyboard command you may want to try is the "H" key, which is a fairly global command for jumping directly to the main menu (aka: 'Home'). I'm not sure if this works from the crash report dialog, but it's worth trying anyway.

Another thing which could help is to use an SSH client (like the freeware PuTTY 0.63) to connect to the RPi, using name and password of "root" and "rasplex", after which you try various commands to restart the RPi, or just the PHT application (eg: "killall plexhometheater").

If breaking the 'crash report loop' doesn't work by any of these methods you may have to pull the power plug to shut the unit down, though that always brings some risk of SD card corruption. But even then I would try plugging it in again, to see if the crash loop has been eliminated, or still recurs.

If after all this the crash looping continues I'd give up and consider that SD card fatally corrupted, in which case reflashing from scratch is the only alternative.

Best regards: dlanor

---

<div class="post-metadata">

**Author:** ![Nibb31](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/nibb31/32/12439_2.png) [@Nibb31](https://forums.plex.tv/u/Nibb31)\
**Post date:** [April 17, 2015, 6:02am UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081/5 "2015-04-17T06:02:46Z")

</div>

Neither rebooting from SSH, nor backing out of the dialog boxes helps. They just keep coming back.

I guess it's reinstall time then...

---

<div class="post-metadata">

**Author:** ![dlanor](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/dlanor/32/4522_2.png) [@dlanor](https://forums.plex.tv/u/dlanor)\
**Post date:** [April 17, 2015, 6:38pm UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081/6 "2015-04-17T18:38:21Z")

</div>

> Neither rebooting from SSH, nor backing out of the dialog boxes helps. They just keep coming back.
> 
> I guess it's reinstall time then...

I'm afraid so. Given your description something must be severely corrupted.

I see no other solution to this than reflashing from scratch... :(

Best regards: dlanor

&nbsp;

---

<div class="post-metadata">

**Author:** ![fthomas152](https://avatars.discourse-cdn.com/v4/letter/f/dc4da7/32.png) [@fthomas152](https://forums.plex.tv/u/fthomas152)\
**Post date:** [June 15, 2015, 8:51pm UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081/7 "2015-06-15T20:51:16Z")

</div>

Just to report in - I have had this issue too, and the only way I could remedy it was re-flashing the SD card.  
  
  
raspberry pi 2, rasplex 0.6.0

---

<div class="post-metadata">

**Author:** ![bofalot](https://avatars.discourse-cdn.com/v4/letter/b/bb73d2/32.png) [@bofalot](https://forums.plex.tv/u/bofalot)\
**Post date:** [January 13, 2016, 9:32pm UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081/8 "2016-01-13T21:32:11Z")

</div>

For others that come across this thread, I was able to remedy this by the slightly less painful method of performing a hard reset (from the system configuration menu). Still not ideal, but better than having to re-flash.

---

<div class="post-metadata">

**Author:** ![j3roen](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/j3roen/32/194022_2.png) [@j3roen](https://forums.plex.tv/u/j3roen)\
**Post date:** [January 12, 2017, 1:37pm UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081/9 "2017-01-12T13:37:27Z")

</div>

It’s a bug, but it’s easily fixed. No need to reinstall. SSH to the rasplex system and empty the /storage/.plexht/temp/CrashReports/\* directory.

(rm -rf /storage/.plexht/temp/CrashReports/\*).

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [January 8, 2020, 6:56pm UTC](https://forums.plex.tv/t/crash-report-submitted-loop/100081/10 "2020-01-08T18:56:27Z")

</div>


