Closed Bug 1599776 Opened 6 years ago Closed 6 years ago

Crash in [@ ErrorLoadingSheet]

Categories

(Core :: Layout, defect, P3)

68 Branch
x86
Windows 10
defect

Tracking

()

RESOLVED DUPLICATE of bug 1463822

People

(Reporter: dmiescher, Unassigned)

Details

Crash Data

This bug is for crash report bp-7274147d-daa4-4c87-854c-f72e20191127.

Top 10 frames of crashing thread:

0 xul.dll static void ErrorLoadingSheet layout/style/nsLayoutStylesheetCache.cpp:500
1 xul.dll nsLayoutStylesheetCache::LoadSheet layout/style/nsLayoutStylesheetCache.cpp:536
2 xul.dll nsLayoutStylesheetCache::UASheet layout/style/UserAgentStyleSheetList.h:36
3 xul.dll mozilla::dom::Document::CreatePresShell dom/base/Document.cpp:3915
4 xul.dll nsresult nsDocumentViewer::InitPresentationStuff layout/base/nsDocumentViewer.cpp:735
5 xul.dll nsresult nsDocumentViewer::InitInternal layout/base/nsDocumentViewer.cpp:979
6 xul.dll nsresult nsDocumentViewer::Init layout/base/nsDocumentViewer.cpp:717
7 xul.dll nsresult nsDocShell::Embed docshell/base/nsDocShell.cpp:6361
8 xul.dll nsresult nsDocShell::CreateAboutBlankContentViewer docshell/base/nsDocShell.cpp:7159
9 xul.dll nsresult nsDocShell::EnsureContentViewer docshell/base/nsDocShell.cpp:7012

The priority flag is not set for this bug.
:jimm, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(jmathies)
Component: Launcher Process → Layout
Flags: needinfo?(jmathies)
Product: Firefox → Core

That is NS_ERROR_FILE_NOT_FOUND. Looks like a corrupt installation, as the ua sheet isn't there? Not sure this is really actionable.

The priority flag is not set for this bug.
:heycam, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cam)

Sounds similar to previous bugs we've seen, though sometimes with different error codes. Duping to the last bug we had open for that.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(cam)
Priority: -- → P3
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.