Closed Bug 973081 Opened 12 years ago Closed 11 years ago

crash in nsCSSFrameConstructor::ConstructRootFrame()

Categories

(Core :: General, defect)

28 Branch
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: vladan, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-cd47bb91-ac7e-43cb-aca8-13bb82140214. ============================================================= I had dozens of tabs open, so I can't provide STR
That stack doesn't make much sense. It seems unlikely that ConstructRootFrame is the actual culprit.
Component: Layout → General
(In reply to Vladan Djeric (:vladan) from comment #0) > bp-cd47bb91-ac7e-43cb-aca8-13bb82140214. > ============================================================= 0 xul.dll nsCSSFrameConstructor::ConstructRootFrame() layout/base/nsCSSFrameConstructor.cpp 1 xul.dll nsFontCache::Init(nsDeviceContext*) gfx/src/nsDeviceContext.cpp 2 xul.dll ResolvePrototype dom/base/nsDOMClassInfo.cpp 3 xul.dll nsBlockFrame::DestroyFrom(nsIFrame*) layout/generic/nsBlockFrame.cpp 4 xul.dll NS_ComposeColors(unsigned int, unsigned int) gfx/src/nsColor.cpp 5 xul.dll mozilla::layers::BasicImageLayer::DeprecatedGetAndPaintCurrentImage(gfxContext*, float, mozilla::layers::Layer*) gfx/layers/basic/BasicImageLayer.cpp 6 xul.dll ComponentValue gfx/src/nsColor.cpp 7 xul.dll gfxWindowsNativeDrawing::BeginNativeDrawing() gfx/thebes/gfxWindowsNativeDrawing.cpp 8 xul.dll nsStyleLinkElement::DoUpdateStyleSheet(nsIDocument*, mozilla::dom::ShadowRoot*, nsICSSLoaderObserver*, bool*, bool*, bool) content/base/src/nsStyleLinkElement.cpp 9 xul.dll nsStyleLinkElement::DoUpdateStyleSheet(nsIDocument*, mozilla::dom::ShadowRoot*, nsICSSLoaderObserver*, bool*, bool*, bool) content/base/src/nsStyleLinkElement.cpp 10 xul.dll nsCSSFrameConstructor::CreatePlaceholderFrameFor(nsIPresShell*, nsIContent*, nsIFrame*, nsStyleContext*, nsIFrame*, nsIFrame*, unsigned __int64) layout/base/nsCSSFrameConstructor.cpp (In reply to Mats Palmgren (:mats) from comment #1) > That stack doesn't make much sense. It seems unlikely that > ConstructRootFrame is the actual culprit. perhaps malicious DLL like bug 609579?
Flags: needinfo?(mats)
A faulty or malicious DLL might have smashed the stack, sure. It might also be a bug in our code doing the same. Or the crash dump itself wasn't written to disk properly or it got damaged somewhere along the way. Or our stack walking code is confused. I don't know. The stack in bug 609579 OTOH does make sense insofar that the call chain ProcessPendingRestyles -> ConstructFramesFromItem is correct. The only thing wrong there is a variable/parameter in the top frame being null for no obvious reason (guessing from bz's comment, since the data is gone now). Not much point keeping either of these bugs open, IMO.
Flags: needinfo?(mats)
agreed. likely invalid. not worth pursuing.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.