Closed Bug 316623 Opened 19 years ago Closed 12 years ago

Stuck Process running RandomStyles hc_nodtdstaff.xml

Categories

(Core :: Web Painting, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: bc, Unassigned)

References

Details

(Keywords: hang, Whiteboard: [sg:dos])

Attachments

(1 file)

Automated RandomStyles testing on WiNXP with today's FF trunk:

http://test.bclary.com/tests/w3.org/2001/DOM-Test-Suite/build/ecmascript/level1/core/files/hc_nodtdstaff.xml
seed=140;skip=255;changesPerInterval=144;interval=246

Eventually the browser stops repainting the window. CPU is at 0%, closing the browser leaves a process running, then attempting to open a new instance of the browser starts a new process even if MOZ_NO_REMOTE is not set.

Guessing on Layout: View Rendering
I am getting similar behavior with the other xml files in the DOM Test Suite with Random Styles. I'll attach the list here along with the Random Styles parameters for testing purposes. This list will become part of the automated fuzzbusting tests.
Keywords: hang
Whiteboard: [sg:dos]
Blocks: ghostproc
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051203 Firefox/1.6a1

I can't reproduce using the URLs in comment 0 and comment 1.  I let the status bar counter go pretty high (20000 and 10000).

Do you still see this bug, and if so, how far does the status bar counter get on each combination of URL and Random Styles parameters?
(In reply to comment #3)

> 
> Do you still see this bug, and if so, how far does the status bar counter get
> on each combination of URL and Random Styles parameters?
> 

Not on trunk, but still on 1.8 branch. It gets to 15375. We can mark it works for me if you think that is best.
Flags: blocking1.8.0.1?
I actually crash with a null dereference at
 nsGridRowLayout::GetGrid() Line 141

Before the crash it stopped repainting and did appear "stuck", but crashed when I attempted to resize the window.
Status: UNCONFIRMED → NEW
Ever confirmed: true
No sign of a fix, not realistic for 1.8.0.1
Flags: blocking1.8.0.2+
Flags: blocking1.8.0.1?
Flags: blocking1.8.0.1-
Not making 1.8.0.2 either :-(
Flags: blocking1.8.0.2+ → blocking1.8.0.2-
QA Contact: ian → layout.view-rendering
Seems likely that this got fixed or was mitigated since anyone last looked at it. Bob - can you still reproduce? Can we open this up and mark it WFM? I wasn't able to see any issues with Firefox 10 on Win 7 in a VM.
I can't reproduce since I don't quite have the same setup as back then. I don't think it will be worth trying to run these exact tests now since Jesse has been running random styles for 7 years and has filed tons of bugs already. -> WFM.
Group: core-security
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Component: Layout: View Rendering → Layout: Web Painting
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: