Questo sito potrebbe offrire funzionalità limitate durante le operazioni di manutenzione per migliorare l'esperienza utente. Se un articolo non risolve il tuo problema e vuoi richiedere supporto, la nostra comunità di supporto è pronta ad aiutarti tramite @FirefoxSupport su Twitter e /r/firefox su Reddit.

Avatar for Username

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Long press > New Tab doesn't restore tabs after Firefox crashes

  • 1 risposta
  • 2 hanno questo problema
  • 68 visualizzazioni
  • Ultima risposta di Paul

possimpible
possimpible
more options

Hello,

I've told to report technical issues on this website.

I've noticed an issue with Firefox iOS where, if Firefox silently crashes and I open a new tab by doing a long press on the iOS home screen, then selecting New Tab, Firefox only opens that new tab and does not restore the previous session and all previously loaded tabs are gone.

That has happened to me multiple times now and I've had to then try and figure out which tabs I had open by going through the browser history, which is pretty annoying.

To prevent that, I'm pretty much not using the long press > new tab functionality at all anymore and instead I open the app first, then open a new tab. Sometimes, I'll open the app, and if the app crashes, THEN I'm asked if I want to restore the session. Then I have to make sure to not accidentally press NO cause it seems there's no way to get that session back afterwards.

I would suggest a few ideas to prevent this issue: - please offer a setting to auto-restore previous sessions after a crash, instead of asking - alternatively, if pressing NO, or opening a new tab from the homescreen with a long press, offer a way to restore a previous session somewhere on the new tab page

Hello, I've told to report technical issues on this website. I've noticed an issue with Firefox iOS where, if Firefox silently crashes and I open a new tab by doing a long press on the iOS home screen, then selecting New Tab, Firefox only opens that new tab and does not restore the previous session and all previously loaded tabs are gone. That has happened to me multiple times now and I've had to then try and figure out which tabs I had open by going through the browser history, which is pretty annoying. To prevent that, I'm pretty much not using the long press > new tab functionality at all anymore and instead I open the app first, then open a new tab. Sometimes, I'll open the app, and if the app crashes, THEN I'm asked if I want to restore the session. Then I have to make sure to not accidentally press NO cause it seems there's no way to get that session back afterwards. I would suggest a few ideas to prevent this issue: - please offer a setting to auto-restore previous sessions after a crash, instead of asking - alternatively, if pressing NO, or opening a new tab from the homescreen with a long press, offer a way to restore a previous session somewhere on the new tab page

Tutte le risposte (1)

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Hi

I am sorry to hear that Firefox for iOS is crashing. I hope that we can help resolve this for you. Before following the steps below, please make sure that you have updated both your iOS device and Firefox for iOS to the latest versions available.

As a first step, close down many of the tabs that you have open to as few as possible. Does this help reduce the incidence of a crash?

If this does not resolve the issue, open the iOS Settings app, select General then iPhone Storage. Find Firefox and select Offload App. Does this help?

Failing that, we will need to look into this in more detail with some logs from inside your copy of Firefox for iOS. This article will walk you through getting both crash logs and Firefox logs. When you have them, please file them here (a GitHub account is required) so that our developers can look into this further for you.

I hope that this helps.