Crash in nsWeakFrame::InitInternal

RESOLVED WORKSFORME

Status

()

Core
Layout
--
critical
RESOLVED WORKSFORME
8 years ago
4 years ago

People

(Reporter: Scoobidiver (away), Unassigned)

Tracking

({crash})

Trunk
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

8 years ago
It is #38 top crasher in 4.0b8 for the last week.

Comments say:
"i cut and paste a text in one page, then problem happen."
"was using google docs and pressed backspace within a document and it closed."
"searching Google images; running MS Publisher and updating Norton AntiVirus"

Signature	nsWeakFrame::InitInternal(nsIFrame*)
UUID	bf1a9573-f298-45be-aa42-81e322110107
Time 	2011-01-07 20:52:29.639990
Uptime	57
Last Crash	62 seconds before submission
Install Age	1100573 seconds (1.8 weeks) since version was first installed.
Product	Firefox
Version	4.0b8
Build ID	20101214170338
Branch	2.0
OS	Windows NT
OS Version	5.1.2600 Service Pack 3
CPU	x86
CPU Info	GenuineIntel family 6 model 28 stepping 2
Crash Reason	EXCEPTION_ACCESS_VIOLATION_READ
Crash Address	0x7
App Notes 	AdapterVendorID: 8086, AdapterDeviceID: 27ae

Frame 	Module 	Signature [Expand] 	Source
0 	xul.dll 	nsWeakFrame::InitInternal 	layout/generic/nsFrame.cpp:275
1 	xul.dll 	nsEventStateManager::PostHandleEvent 	content/events/src/nsEventStateManager.cpp:3238
2 	xul.dll 	PresShell::HandleEventInternal 	layout/base/nsPresShell.cpp:6962
3 	xul.dll 	PresShell::HandlePositionedEvent 	layout/base/nsPresShell.cpp:6773
4 	xul.dll 	PresShell::HandleEvent 	layout/base/nsPresShell.cpp:6623
5 	xul.dll 	nsViewManager::DispatchEvent 	view/src/nsViewManager.cpp:1070
6 	xul.dll 	AttachedHandleEvent 	view/src/nsView.cpp:193
7 	xul.dll 	nsWindow::DispatchEvent 	widget/src/windows/nsWindow.cpp:3619
8 	xul.dll 	nsWindow::DispatchWindowEvent 	widget/src/windows/nsWindow.cpp:3642
9 	xul.dll 	nsWindow::DispatchMouseEvent 	widget/src/windows/nsWindow.cpp:4066
10 	xul.dll 	nsWindow::ProcessMessage 	widget/src/windows/nsWindow.cpp:4938
11 	xul.dll 	nsWindow::WindowProcInternal 	widget/src/windows/nsWindow.cpp:4456
12 	xul.dll 	nsWindow::WindowProc 	widget/src/windows/nsWindow.cpp:4408
13 		@0xc6b8b680 	
14 	xul.dll 	nsIMM32Handler::ProcessMessage 	widget/src/windows/nsIMM32Handler.cpp:401
15 	xul.dll 	xul.dll@0x3622cd 	
16 	user32.dll 	InternalCallWinProc 	
17 	xul.dll 	nsIMM32Handler::ProcessMessage 	widget/src/windows/nsIMM32Handler.cpp:401
18 	xul.dll 	nsIMM32Handler::ProcessMessage 	widget/src/windows/nsIMM32Handler.cpp:401
19 	user32.dll 	StringDuplicateW 	
20 	user32.dll 	UserCallWinProcCheckWow 	
21 	user32.dll 	DispatchMessageWorker 	
22 	xul.dll 	nsIMM32Handler::ProcessMessage 	widget/src/windows/nsIMM32Handler.cpp:401
23 	user32.dll 	GetShellWindow 	
24 	user32.dll 	NtUserPeekMessage 	
25 	user32.dll 	StringDuplicateW

More 4.0b8 reports at:
http://crash-stats.mozilla.com/report/list?range_value=4&range_unit=weeks&signature=nsWeakFrame%3A%3AInitInternal%28nsIFrame*%29&version=Firefox%3A4.0b8
All of the stacks seem to have IME on the stack. Most of them seem to be processing a key down event (but not stack pasted in this bug, thats a mouse event curiously) but in nsEventStateManager::PostHandleEvent we're always processing a NS_DRAGDROP_EXIT event. From there we goto the crash in nsWeakFrame::InitInternal, but I can't see how we get there (even looking inside the GenerateDragDropEnterExit call).
Can we look at crash data for nightlies to see when this started to maybe get an idea of what changes affected this?
(Reporter)

Comment 3

8 years ago
There is no clear regression, it has happened continiously for one month (no stats before) at the same crash daily rate (~2-3 crashes/buildday).
It exists in 3.6.13 but its ranking as a crasher is higher than 300.
So the regression is older than one month.
(Assignee)

Updated

7 years ago
Crash Signature: [@ nsWeakFrame::InitInternal(nsIFrame*) ] [@ nsWeakFrame::InitInternal ]
(Reporter)

Updated

7 years ago
Crash Signature: [@ nsWeakFrame::InitInternal(nsIFrame*) ] [@ nsWeakFrame::InitInternal ] → [@ nsWeakFrame::InitInternal(nsIFrame*) ] [@ nsWeakFrame::InitInternal ]
Hardware: x86 → All
happening everytime with Ubuntu 12.10 and Firefox 16.0.1 when i logging on facebook 

crash id bp-3548b200-3b90-4c00-aa6d-b4c9c2121102
(Reporter)

Comment 5

6 years ago
(In reply to Swarnava Sengupta (:Swarnava) from comment #4)
> crash id bp-3548b200-3b90-4c00-aa6d-b4c9c2121102
This stack trace is likely bug 787818 and has something to do with hiding popups.
Summary: Crash [@ nsWeakFrame::InitInternal(nsIFrame*) ] [@ nsWeakFrame::InitInternal ] → Crash in nsWeakFrame::InitInternal
(In reply to Swarnava Sengupta (:Swarnava) from comment #4)
> happening everytime with Ubuntu 12.10 and Firefox 16.0.1 when i logging on
> facebook 

I use Ubuntu and I don't see any crashes loading facebook. Maybe it is an addon you have installed? Could you try a fresh profile and see if you have the same problem? That would help narrow it down.
(In reply to Timothy Nikkel (:tn) from comment #6)
> (In reply to Swarnava Sengupta (:Swarnava) from comment #4)
> > happening everytime with Ubuntu 12.10 and Firefox 16.0.1 when i logging on
> > facebook 
> 
> I use Ubuntu and I don't see any crashes loading facebook. Maybe it is an
> addon you have installed? Could you try a fresh profile and see if you have
> the same problem? That would help narrow it down.

tried with reset Firefox, create new profile! no luck! i have no addon installed! i just installed ubuntu today morning!

Comment 8

6 years ago
I’ve had these crashes last week while looking at the issues with SUMO KB’s editor “ACE” that I’ve described in bug 825425 comment 0:
bp-1e6a5425-2613-4713-825d-545262121229
bp-75f3e107-19cb-4853-afea-127022121229

Comment 9

6 years ago
(In reply to Aleksej [:Aleksej] from comment #8)
(that’s Firefox 18.0b6)

Comment 11

6 years ago
Here is another crash report: https://crash-stats.mozilla.com/report/index/bp-5996997a-b502-46db-b650-dca882130130

Occurred when watching (Flash) videos on CNN.
There are very few reports of this signature recently.  All of them are from FF26 or older (most are
for ancient versions like FF4.0.*).
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.