1434228 - After Upgrading to TB 52.6 Lightning is not coming up. Reboot of Windows fixes it. Caused by shutdown hang?

Status: RESOLVED INCOMPLETE

(Calendar :: General, defect)

Description

[Maarten van der Upwich]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36

Steps to reproduce:

Automatically upgraded to TB 52.6 coming from 52.5.8 (I think) 


Actual results:

After restart Lightning is not coming up anymore. Reverted back to TB 52.2.8 and now it works again. But even in 52.5 Lightning didn't always started correctly and had many times first reboot W7 for it to start working again.


Expected results:

Lightning should come up.

Comment 1

[Wayne Mery (:wsmwk)]

There is no such thing as 52.5.8 or 52.2.8.  
There is a 52.5.2, which is likely what you were running before 52.6.0.

I have never heard of rebooting windows to help Lightning start.  Has anyone else?

Comment 2

[Maarten van der Upwich]

Apologies; wasn't sure about the previous version.

If you search the Internet you will find several articles about the same problem where rebooting W7 solved the issue. That saved me!

Comment 3

[Wayne Mery (:wsmwk)]

Restarting Thunderbird is known to help. But restarting Windows is new to me. Can you cite URL of some articles that claim this?

Comment 4

[Maarten van der Upwich]

This is the article that triggered me to restart W7 and it worked (on 52.5.2). Rebooting didn't help on 52.6.0, hence my downgrade and disabling automatic upgrades).
https://support.mozilla.org/en-US/questions/1179954

Comment 5

[Wayne Mery (:wsmwk)]

(In reply to Maarten van der Upwich from comment #4)
> This is the article that triggered me to restart W7 and it worked (on
> 52.5.2). Rebooting didn't help on 52.6.0, hence my downgrade and disabling
> automatic upgrades).
> https://support.mozilla.org/en-US/questions/1179954

Thanks the link.  

That reboot was only helpful in conjunction with deleting the lightning folder per  https://support.mozilla.org/en-US/questions/1179954#answer-1017544

Comment 6

[Maarten van der Upwich]

It just happened again; reboot of W7 resolved it. Is there a way to debug this once this happens?

Comment 7

[Wayne Mery (:wsmwk)]

Ever heard of rebooting helping?
Antivirus?

Comment 8

[Matt]

My experience is a reboot only helps where there is a shut down hang so subsequent restarts do not restart, just redisplay the already running kernel.  Most shut down hangs do appear to be anti virus related, so there may be anti virus in the background responsible.  It is easy to check the windows task manager in these instances. 

It is also worth disabling global search in options if a process is continuing post shut down  just t see if a corrupt SQLite database is involved as has been the case with me a couple of times. (I assume corruption as the process just kept on ticking)

Comment 9

[Wayne Mery (:wsmwk)]

Maarten, any further conclusions about your situation?

Comment 10

[Maarten van der Upwich]

Hi, I have been using TB V45.0 and haven't upgraded since anymore. So, I'm not sure what the current situation is.

Comment 11

[Wayne Mery (:wsmwk)]

Thanks.  If it is caused by a shutdown hang, then that's the core issue that interests us - and does have various bug reports.
In that case, let's close this as incomplete until information about new versions is forthcoming