1235096 - startup crash in nsCharTraits<T>::compareLowerCaseToASCIINullTerminated with hardware acceleration enabled

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect, P3)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

This bug was filed from the Socorro interface and is 
report bp-efe0bb80-a700-4d9b-a344-576342151224.
=============================================================

Firefox Nightly 46.0a1 20151224030228 32 bit on Windows 8.1 64 bit with Nvidia 765M driver version 359.06 and Intel Haswell i7-4700MQ

Launching Nightly crashes on startup with
 0 	xul.dll	nsCharTraits<wchar_t>::compareLowerCaseToASCIINullTerminated(wchar_t const*, unsigned int, char const*)	xpcom/string/nsCharTraits.h
1 	xul.dll	nsAString_internal::LowerCaseEqualsASCII(char const*)	xpcom/string/nsTSubstring.cpp
Ø 2 	nvd3d9wrap.dll	nvd3d9wrap.dll@0x2b86	
3 	xul.dll	nsHtml5TreeBuilder::isQuirky(nsIAtom*, nsString*, nsString*, bool)	parser/html/nsHtml5TreeBuilder.cpp 
...

If I remember correct, after the partial update to 20141224 Nightly launched the first time without issues. After upgrading the Nvidia graphics driver to 361.43 (which involved a restart of the computer), the issue was gone. The used graphics card is the integrated Intel one.

Comment 1

[u279076]

Sebastian, please do the following:
1) Confirm you are using the latest NVidia *and* Intel drivers.
2) Confirm if Nightly crashes on a new profile with no alteration from the default config.
3) Confirm if an older Nightly from https://archive.mozilla.org/pub/firefox/nightly/2015/12/ crashes.
4) See if you can regress this further using mozregression [http://mozilla.github.io/mozregression/install.html]

Thanks

Note to developers:
Here is the pushlog assuming this regressed in today's Nightly (a fact that remains to be proven).
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=ad16863d1d45bd3fd7906c76fa1ac1e12d24a133&tochange=35b211eaad1fa828064514c547057e4400e24459

Comment 2

[u279076]

[Tracking Requested - why for this release]: new crash could prevent some user from starting Nightly, although volume is extremely low at this point (85th topcrash @ 0.2%).

Comment 3

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

When the issue occurred, I was able to reproduce it
a) with a new profile
b) after downloading the full installer and installing it in the same directory.

After the Windows restart, I am not anymore able to reproduce it (downgraded the Nvidia graphics driver and then went back to the latest version, but no crashes observed). There is a newer version of the Intel driver 15.36.28.4332 ( https://downloadcenter.intel.com/download/25588/Intel-Grafik-Treiber-f-r-Windows-7-8-1-15-36-28-4332- ) but that doesn't get served by Windows Update yet.

https://crash-stats.mozilla.com/report/list?product=Firefox&signature=nsCharTraits%3CT%3E%3A%3AcompareLowerCaseToASCIINullTerminated says it's also occurring in Firefox 38.4.0, so that's likely no (recent) regression but a graphics driver in a state where it returns something unexpected.

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

This was the #1 topcrash in yesterday's (December 24) Windows mozilla-central nightly.

Comment 5

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

For what it's worth, 7 of these 14 crashes are by me. Because I have no steps to reproduce, I will go ahead and update the Intel HD drivers to version 15.36.28.4332 which doesn't get shipped yet by Windows Update unless someone objects with an idea how to reproduce the issue.

Comment 6

[Liz Henry (:lizzard) (relman/hg->git project)]

No longer a top crash in Nightly. There are only 3 crashes with this signature right now for the past week. 
If we can reproduce this, we could potentially block the problematic driver. 

For now, I don't think this needs to be tracked.

Comment 7

[David Anderson [:dvander] - inactive, e-mail if emergency]

Taking the topcrash keyword off, as it looks like this is super low volume now.

Comment 8

[Peter Chang[:pchang]]

Only saw 20 crashes this week, lower the priority.

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.