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!

Avatar for Username

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

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Using Aurora on Ubuntu, there is no way to "restart" when multiple profiles.

  • 1 Antwort
  • 1 hat dieses Problem
  • 1 Aufruf
  • Letzte Antwort von guigs

HenryGR
HenryGR
more options

Currently using Aurora [Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 ID:20140804085133 CSet: Undefined] on Ubuntu 14.04

Whenever I install a new Addon and need to restart, Aurora simply closes ang gets 'hangged' on memory without restarting.

This happens since I have two different profiles [currently one with a full-charge of addons, and one that uses no addons].

Currently using Aurora [Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 ID:20140804085133 CSet: Undefined] on Ubuntu 14.04 Whenever I install a new Addon and need to restart, Aurora simply closes ang gets 'hangged' on memory without restarting. This happens since I have two different profiles [currently one with a full-charge of addons, and one that uses no addons].

Geändert am von HenryGR

Alle Antworten (1)

guigs
guigs
more options

Hi HenryGR, Thank you for your question.

Please make sure in both profiles that the extensions are up to date: Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

Also let's start here for general hanging, even though it may have to do with a process happening there: https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding#w_fi...

What are the results after these troubleshooting steps?