Closed Bug 1490653 Opened 6 years ago Closed 6 years ago

Firefox crashes on startup via mozilla::net::CacheEntry::GetSecurityInfo using any profile visited by Firefox Nightly (64)

Categories

(Core :: Security: PSM, defect)

defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1490585
Tracking Status
firefox-esr60 --- fixed
firefox62 --- fixed
firefox63 - fixed
firefox64 - unaffected

People

(Reporter: emilghitta, Unassigned)

References

Details

(Keywords: crash, regression, topcrash, Whiteboard: [tbird topcrash])

Crash Data

This bug was filed from the Socorro interface and is
report bp-a015cfb9-419e-43b0-ba05-a0c800180912.
=============================================================

Top 10 frames of crashing thread:

0 xul.dll nsSSLStatus::~nsSSLStatus security/manager/ssl/nsSSLStatus.h:34
1 xul.dll nsSSLStatus::Release security/manager/ssl/nsSSLStatus.cpp:387
2 xul.dll mozilla::psm::TransportSecurityInfo::~TransportSecurityInfo security/manager/ssl/TransportSecurityInfo.h:35
3 xul.dll mozilla::psm::TransportSecurityInfo::`scalar deleting destructor' 
4 xul.dll mozilla::psm::TransportSecurityInfo::Release security/manager/ssl/TransportSecurityInfo.cpp:50
5 xul.dll nsBinaryInputStream::ReadObject xpcom/io/nsBinaryStream.cpp:989
6 xul.dll NS_DeserializeObject netwerk/base/nsSerializationHelper.cpp:48
7 xul.dll mozilla::net::CacheEntry::GetSecurityInfo netwerk/cache2/CacheEntry.cpp:1365
8 xul.dll mozilla::net::nsHttpChannel::OpenCacheInputStream netwerk/protocol/http/nsHttpChannel.cpp:4698
9 xul.dll mozilla::net::nsHttpChannel::OnCacheEntryCheck netwerk/protocol/http/nsHttpChannel.cpp:4209

=============================================================
[Affected platforms]:
Windows 10 64bit.
macOS 10.13.4

[Steps to reproduce]:
1. Launch Firefox Nightly 64.0a1 (BuildId:20180911224301) with a new profile.
2. Close Firefox.
3. Open Firefox 62.0 (BuildId:20180830143136) with the same profile from step 1.

[Expected result]:
Firefox runs successfully.	

[Actual result]:
Firefox crashes.

[Regression range]:
I will try to search for a regression asap.

[Note]
For further information regarding this issue please observe the following screencast: https://drive.google.com/open?id=1CLm0F1_41k4UIJGood6jR87cxv1ULunX
Please feel free to change the component if necessary.
It seems that Firefox crashes if the same profile is launched with Firefox Beta 63 as well.
I just got that too.

I was using Firefox (stable) then decided to try a website but with webrender, so i closed firefox stable and opened Nightly, turned on Webrender, restarted, tried my site, disabled webrender, closed Nightly, and re opened Firefox stable, but Firefox stable now crashes 1 second after startup constantly, so i re opened Nightly and it crashes too, so i make a new Profile and opens Nightly on it, doesn't crash and downloads another update, now it doesn't crash on the profile i use but Firefox stable still crashes.

Important: Nightly installed an update while i restarted it to turn on Webrender, so there was 2 updates.

https://crash-stats.mozilla.com/report/index/8ec0e2d0-e5a1-4c16-a06c-5eed10180912
Blocks: 1468222
Crash Signature: [@ nsSSLStatus::~nsSSLStatus] → [@ nsSSLStatus::~nsSSLStatus] [@ Gecko_SetLengthString] [@ nsNSSCertificate::GetIssuerCommonName] [@ nsTSubstring<T>::SetCapacity]
Component: General → Security: PSM
Summary: Crash in nsSSLStatus::~nsSSLStatus → Firefox crashes on startup using any profile visited by Firefox Nightly (64)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Not tracking for 63 as we are already tracking bug 1490585
Since the real bug is hidden (behind security issue firewall I assume) it would be good to have a workaround listed here for people whose profiles are afflicted with the Nightly Plague.

Disabling session restore and disabling hardware acceleration both don't fix it. Entirely clearing your cache makes it possible to start previous versions of firefox without crashing, but SSL is permanently hosed - I can't load gmail anymore without the tab crashing.
You might have to clear service workers as well?
In any case, avoid using the same profile on nightly and beta/release.
That isn't really a good solution here since a single run of nightly will eat your profile unless you manage to avoid ever opening it by accident without passing -P. I recall developer edition defaulted to a separate profile, it might be nice to make nightly do that too in a future release to avoid other people having this happen to their profiles when they install to try out webrender.
See Also: → 1492491
Summary: Firefox crashes on startup using any profile visited by Firefox Nightly (64) → Firefox crashes on startup via mozilla::net::CacheEntry::GetSecurityInfo using any profile visited by Firefox Nightly (64)
Whiteboard: [tbird topcrash]
You've probably already discovered it, but deleting cache worked for me (workaround).
"cache" on Windows meaning the stuff stored in C:\Users\xxx\AppData\Local\Mozilla\Firefox\Profiles, right?
yes
Bug 1490585 is still hidden. Is the problem supposed to be fixed in Nightly? My profile is now unusable due to crashes and I'm wondering if I should create a new bug report or if bug 1490585 is still in progress.
Which version of which program are you using?
I updated this morning, so probably the second Nightly from yesterday. I saw the problem with the ASan Nightly and the regular Nightly.

Build ID 	20180827220123 

I'm sorry, I should have pointed to the crashes with my last message.

Many with stacks like this: https://crash-stats.mozilla.com/report/index/d44be04d-0267-4fe4-838e-688d40181018
One like this: https://crash-stats.mozilla.com/report/index/3155cd82-4dda-4c08-95a3-094d10181018
(In reply to B.J. Herbison from comment #14)
> Many with stacks like this:
> https://crash-stats.mozilla.com/report/index/d44be04d-0267-4fe4-838e-
> 688d40181018
> One like this:
> https://crash-stats.mozilla.com/report/index/3155cd82-4dda-4c08-95a3-
> 094d10181018

Those crashes are from old nightly builds (from over a month ago).
Sorry to bother you. Nightly wouldn't update since it was always crashing, and ASan Nightly doesn't store crashes so I didn't get a crash report from those hangs I stopped with SIGABRT.

I updated Nightly with a new profile and now it doesn't crash, even for the previous profile. I got in some bad state with ASan Nightly and now I can't reproduce it. (Not an out-of-memory problem, I checked.)
You need to log in before you can comment on or make changes to this bug.