99430 - Crash (null data pointer) in JSDOM.DLL

Status: RESOLVED WORKSFORME

(Core :: Layout, defect)

Description

[Peter Jones]

Occurred while surfing Intel site and looking at 2 GHz processor, then clicking
to  Dell site (possible vendor)
I'm on Mozilla Build 2001080110.
Will upload DrWatson dump.

Comment 1

[Peter Jones]

Attachment: DrWatson dump of JSDOM crash

Comment 2

[Peter Jones]

Full Circle feedback also sent to Netscape (don't know if that's useful).

Comment 3

[Boris Zbarsky [:bzbarsky]]

Peter, Full Circle should give you a "Talkback id" for the feedback it sent.  Do
you happen to have that?  Can you put it in this bug?

Comment 4

[Peter Jones]

I didn't jot down the Talkback Id, so unless a log of it was left on my machine,
I don't know where to find it. I think I posted my bug report within a couple of
hours of sending the report; probably my IP address was the same too, for I use
a cable modem.

Otherwise, I'll have to remember to jot down the Talkback Id. Sorry I can't be
of more help.

Comment 5

[Johnny Stenback (:jst)]

Unfortunately I'm unable to find the talkback report that was submitted on this.
Could you provide more info about the talkback report, e.g. email address used,
comment, IP address. W/o more info I'll haveto mark this WORKSFORME.

Comment 6

[Peter Jones]

Additional info:
Remark on Dr Watson file:
"Null data pointer while surfing intel pentium site re 2 Ghz processor, then
Dell site"
I don't know if that's in the Talkback file too. I don't think I put in an
e-mail address. Try lokking for [e-mail], or [e-mail].

My system info was (and still is):
Microsoft Windows 98.4.10.1998
Clean install using OEM Preinstall Kil
IE 5.50.4807.2300

Uptime 0:17:51.53 Normal mode
On "JONES" as "default"

Genine Intel Pentium II MMX
64MB RAM

Custom swap file on disk D
My IP address is now 24.202.157.71, on a cable modem with ISP Videotron, Canada.
I don't know if it has changed since.

Command line: "F:\mozilla.org\Mozilla\mozilla.exe" -url ""

Hope this provides enought clues. Please let me know which clue worked best.
I suggest you start with the computer name, and command line.

Comment 7

[Johnny Stenback (:jst)]

I tried to find this incident report in our talkback system with all the clues
from the above comment, but I can't find it. Either the talkback system never
got the report, or the talkback system lost the report. Either way, not much I
can do here :-(

WORKSFORME.

Comment 8

[Peter Jones]

I have two ID's for you to check:
I don't have a comment in either.
TB35320143X and TB35317784K. The capture date is shown as the day following my
initial filing (maybe Talkback times are GMT, and I'm on EDT, four hours behind).

Talkback is offering me the possibility of sending these, if you don't have them.

Comment 9

[Sivakiran Tummala]

did not crash on win 2000 and win 95

Comment 10

[Asa Dotzler [:asa]]

Incident ID 35320143
Stack Signature nsFrame::GetOffsetFromView 588a295a
Bug ID
Trigger Time 2001-09-13 01:10:55
Email Address [e-mail]
User Comments
Build ID 2001080112
Product ID MozillaTrunk
Platform ID Win32
Trigger Reason Access violation
Stack Trace
nsFrame::GetOffsetFromView
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsFrame.cpp, line 2122]
nsCaret::GetViewForRendering
[d:\builds\seamonkey\mozilla\layout\base\src\nsCaret.cpp, line 751]
nsCaret::DrawCaret [d:\builds\seamonkey\mozilla\layout\base\src\nsCaret.cpp,
line 908]
nsCaret::StartBlinking [d:\builds\seamonkey\mozilla\layout\base\src\nsCaret.cpp,
line 456]
nsCaret::SetCaretVisible
[d:\builds\seamonkey\mozilla\layout\base\src\nsCaret.cpp, line 210]
PresShell::SetCaretEnabled
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 2996]
PresShellViewEventListener::RestoreCaretVisibility
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 6757]
PresShellViewEventListener::DidRefreshRegion
[d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 6792]
nsViewManager::Refresh [d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp,
line 938]
nsViewManager::DispatchEvent
[d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 1960]
HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 68]
nsWindow::DispatchEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 725]
nsWindow::DispatchWindowEvent
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 747]
nsWindow::OnPaint [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp,
line 4051]
nsWindow::ProcessMessage
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3038]
nsWindow::WindowProc
[d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 990]
KERNEL32.DLL + 0x363b (0xbff7363b)
KERNEL32.DLL + 0x242e7 (0xbff942e7) 

Comment 11

[Johnny Stenback (:jst)]

Looks like this is a crash in layout code, accoding to the stacktrace at least.
Over to layout, but I'm afraid this is a WORKSFORME bug, unless someone can
reproduce this crash.

Comment 12

[Kevin McCluskey (gone)]

Resolving as WFM. Please reopen if you can reproduce the crash.