Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Firefox crashes whenever I connect my Sync account to my phone

  • 6 Antworten
  • 3 haben dieses Problem
  • 2 Aufrufe
  • Letzte Antwort von philipp

more options

Over the past week or so, I have been struggling with using Firefox paired with my Sync account, for it has crashed randomly whenever I am connected to the Internet (my phone's connectivity is only part-time.)

Specs: Starmobile KNIGHT X, KitKat

Over the past week or so, I have been struggling with using Firefox paired with my Sync account, for it has crashed randomly whenever I am connected to the Internet (my phone's connectivity is only part-time.) Specs: Starmobile KNIGHT X, KitKat

Alle Antworten (6)

more options

hi bonarae, can you type about:crashes into the address bar of your firefox on android and paste the latest few crash ids into a reply here in the forum? thank you!

more options
more options

thank you. this appears to be a crash on some less common devices triggered by sync that is being investigated by mozilla's developers at the moment.

could you try to replicate the issue by using a current firefox 38 aurora build which is available as .apk from https://wiki.mozilla.org/Mobile/Platforms/Android#Download_Aurora if so can you get the id of the crash signature again and report it here as well?

many thanks and sorry about the issue...

more options
more options

Still having the issue as of the latest Aurora build.

more options

hi bonarae, yes unfortunately it's an ongoing issue still (you could also follow along in bug #1138943). maybe the developers working on fixing this would want to get in contact with you to gather some more information on the issue...