User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce: i use firefox and rkiosk to do a google slideshow at work. we have a frame reloader that keeps it up to date but the browser crashes every few days and gets hung up on the crash reporter. also: i use this on raspberry pi, ubuntu, and, android. Actual results: crash reporter prevents loop script run from startup script from restarting firefox on fail. NOTE i dont care how firefox restarts as long as it doesn't have a resume prompt. i prefer it just fail and let my script restart it after breakpad has been disabled. Expected results: option boxes on crash report window for default action(send/dont, restart/close) and check box for don't show this again.
Component: Untriaged → Breakpad Integration
Product: Firefox → Toolkit
lol thought that said userless ui. should prop fix that. it would be nice to see kiosk in the list of keywords. arm or raspberry pi would be nice to see aswell. (low ram systems) don't care that firefox crashes under this page. just want it close after so script can restart it with url so no restore prompt either.
should be a simple fix, just need checkboxes for send/dont and close/restart as well as one for don't show this again(save as default choices) changeable under settings of course.
sorry just making sure i'm clear. all i want is if firefox crashes it will not prompt for crash report at all just close and let my script restart it with a url param and then not have to fear restore session throwing a prompt at startup. this is for a kiosk so every prompt that doesn't have a don't show this again is a bane to my existence.
also it may take from 10 min to 4 days to crash. so dont focus on crash. just failing gracefully in user-less environment. thank you for trying :-)
Summary: need option to hide promp for breakpad and allow script to restart kiosk page on crash → need option to hide prompt for breakpad and allow script to restart kiosk page on crash
You need to log in before you can comment on or make changes to this bug.