We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Avatar for Username

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

Thunderbird (60.6.1) on Windows 10 (v1809) will not start again after terminating, reporting "Thunderbird is already running, but is not responding."

  • 1 wótegrono
  • 1 ma toś ten problem
  • 3 naglědy
  • Slědne wótegrono wót sfhowes

Alchemist990
Alchemist990
more options

Recently, after terminating Thunderbird (60.6.1) on Windows 10 (v1809), it will not start again, reporting: "Thunderbird is already running, but is not responding. The old Thunderbird process must be closed to open a new window".

W10 Resource Monitor shows that process components remain in memory, long after thunderbird.exe has terminated.

I also have a similar problem with Firefox (v66.0.3), showing the same failure to eliminate Forefox components from memory after termination, and the same failure to restart.

The only way I have found to fix the problem is to reboot. Ugh!

Recently, after terminating Thunderbird (60.6.1) on Windows 10 (v1809), it will not start again, reporting: "Thunderbird is already running, but is not responding. The old Thunderbird process must be closed to open a new window". W10 Resource Monitor shows that process components remain in memory, long after thunderbird.exe has terminated. I also have a similar problem with Firefox (v66.0.3), showing the same failure to eliminate Forefox components from memory after termination, and the same failure to restart. The only way I have found to fix the problem is to reboot. Ugh!
Pśipowjesone fota wobrazowki

Wšykne wótegrona (1)

sfhowes
sfhowes
  • Top 10 Contributor
more options

Try removing the profile lock file:

http://kb.mozillazine.org/Profile_in_use#Remove_the_profile_lock_file

Works for TB and Firefox.