Crash, on scrolling on page which might not have been fully rendered? [@ GetHeightOfRowsSpannedBelowFirst(nsTableCellFrame&, nsTableFrame&) ]

RESOLVED INCOMPLETE

Status

()

--
critical
RESOLVED INCOMPLETE
9 years ago
8 years ago

People

(Reporter: educmale, Unassigned)

Tracking

({crash, crashreportid})

1.9.2 Branch
x86
Windows XP
crash, crashreportid
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature, URL)

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)

I often click on URLs, and then switch to the new tabs which are generated.   Sometimes, I will scroll as the page is being generated, and there are crashes

This time, I think all tabs were in place and fully rendered, and I [probably] was scrolling [using the mouse] as I read down the page.   I am assuming that the page had been fully rendered, and Fox did not need to have me visualize [bring into the Windows' window] to notice that further processing/rendering was necessary.  However, I don't -know- that to be a fact, and thus I have suspicions about what is going on.

This kind of behavior happens, now and then...sometimes just crashing while I am not even doing anything, although I can't be absolutely certain that the mouse is "nibbling", due to the surface on which it sits not letting the LED feedback to be still.

bp-9ec5edbd-662b-4122-9de8-251af2100217

http://crash-stats.mozilla.com/report/index/bp-9ec5edbd-662b-4122-9de8-251af2100217

Reproducible: Sometimes

Steps to Reproduce:
1.   Read on a page
2.
3.
Does this also happen in safe-mode / with a new profile?
http://support.mozilla.com/en-US/kb/Safe+Mode
http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile
Keywords: crash, crashreportid
Summary: Crash, on scrolling on page which might not have been fully rendered? → Crash, on scrolling on page which might not have been fully rendered? [@ GetHeightOfRowsSpannedBelowFirst(nsTableCellFrame&, nsTableFrame&) ]
Version: unspecified → 3.6 Branch
(Reporter)

Comment 2

9 years ago
It has happened in safe mode.  Though, in use, when the crashes occur, I am just plain old using Fox, so I tend to be in standard mode most of the time...

I have not made a new profile.  The thought of that makes me wonder what about a profile could cause a crash in the rendering engine?

Also...a recommendation, though not sure where to place it:  it might be helpful to have the error console trap the date/time of the errors, as it now occurs to me I could have back tracked to an error aligned in time, there, with the time of my crashes

Updated

9 years ago
Component: General → Layout: Tables
Product: Firefox → Core
QA Contact: general → layout.tables
Version: 3.6 Branch → 1.9.2 Branch
Bernd, any idea what might be going on here?
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 4

9 years ago
I bet its a deleted cellFrame, although it doesn't ring a bell. The steps to reproduce are not clear enough to start any action on this. The only thing that I see is Tab Mix Plus 0.3.8.2  which would correspond to

>I often click on URLs, and then switch to the new tabs which are generated.  
>Sometimes, I will scroll as the page is being generated, and there are crashes
(Reporter)

Comment 5

9 years ago
See  Bug 547230

Comment 6

9 years ago
although there is crash id if no steps are defined that invoke the crash this thing heads down the WFM or more precisely the INCOMPLETE path. Bonus points are give if this behavior can triggered on the nightlies.

Comment 7

9 years ago
marking this as incomplete as there are no steps to see this on trunk. Please reopen if you can reproduce this with a nightly.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
Crash Signature: [@ GetHeightOfRowsSpannedBelowFirst(nsTableCellFrame&, nsTableFrame&) ]
You need to log in before you can comment on or make changes to this bug.