Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Scrolling bookmarks causes iOS app to crash

  • 2 odgovora
  • 2 imaju ovaj problem
  • 1 prikaz
  • Posljednji odgovor od carl.graziano

more options

Attempted to scroll through a folder of bookmarks (Firefox for iOS on an older iPad Pro that’s been fully updated to iOS 16.1). About halfway through the scroll, the app shuts down. Upon restart, it restores tabs, but also apparently clears cache, forcing me to re-login to accounts.

Attempted to scroll through a folder of bookmarks (Firefox for iOS on an older iPad Pro that’s been fully updated to iOS 16.1). About halfway through the scroll, the app shuts down. Upon restart, it restores tabs, but also apparently clears cache, forcing me to re-login to accounts.

Izabrano rješenje

Hi

I am sorry to hear that Firefox for iOS is crashing. I hope that we can help resolve this for you.

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 help, open the iOS Settings app, find Firefox and select Clear History and Website Data. 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:

  1. Launch Firefox.
  2. Open Settings.
  3. Scroll down to Version and tap it several times.
  4. Scroll down and hit "Debug: copy log files to app container". This triggers the logs to be saved into the Documents folder.
  5. Open the Files App on your iOS device and navigate to Fennec > Logs. You can see the different logs files here, which you can export using the share menu from Apple to a desktop computer.
  6. Open the file and replace any email address with XXXXXXXXX - and keep a copy of this report.
  7. Copy and past the full report into https://paste.mozilla.org/, setting the two options at the top to Plain Text and Expire in one week.
  8. Select Paste Snippet on the right hand side, then copy and past the link into a reply to this thread.

I hope that this helps.

Pročitaj ovaj odgovor u kontekstu 👍 1

Svi odgovori (2)

more options

Odabrano rješenje

Hi

I am sorry to hear that Firefox for iOS is crashing. I hope that we can help resolve this for you.

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 help, open the iOS Settings app, find Firefox and select Clear History and Website Data. 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:

  1. Launch Firefox.
  2. Open Settings.
  3. Scroll down to Version and tap it several times.
  4. Scroll down and hit "Debug: copy log files to app container". This triggers the logs to be saved into the Documents folder.
  5. Open the Files App on your iOS device and navigate to Fennec > Logs. You can see the different logs files here, which you can export using the share menu from Apple to a desktop computer.
  6. Open the file and replace any email address with XXXXXXXXX - and keep a copy of this report.
  7. Copy and past the full report into https://paste.mozilla.org/, setting the two options at the top to Plain Text and Expire in one week.
  8. Select Paste Snippet on the right hand side, then copy and past the link into a reply to this thread.

I hope that this helps.

more options

Clearing history and website data seems to have fixed it. Thanks!