586996 - Hang on windows running a JS demo and dragging the browser window

Status: RESOLVED DUPLICATE of bug 575515

(Core :: Graphics, defect)

Description

[(not currently active) Ted Mielczarek]

STR:
1) Load the URL provided
2) Drag the browser window by the titlebar

After doing this, my browser is locked up, and it hangs most of my system. The only way out for me is to Ctrl+Alt+Del. That unsticks things until I try to drag the browser again. I attached a debugger while it was hung and the main thread was just deep in JITted code.

Comment 1

[David Mandelin [:dmandelin]]

How did you attach the debugger while it was hung? Clicking on Visual Studio (or anything else) has no effect for me when it's hung.

Comment 2

[(not currently active) Ted Mielczarek]

I...don't recall what I did now. That stack may simply be what the browser was doing after I un-hung things using Ctrl+Alt+Del. Remote debugging might be more useful here.

Comment 3

[bomfog]

On Vista, just Alt+Tab is enough to unfreeze things.

Mozilla/5.0 (Windows NT 6.0; rv:2.0b5pre) Gecko/20100826 Minefield/4.0b5pre NOT Firefox/3.6 - Build ID: 20100826130319

Comment 4

[David Mandelin [:dmandelin]]

URL now goes to nothing.

Comment 5

[(not currently active) Ted Mielczarek]

I emailed the author, I'll update if I get a new URL.

Comment 6

[(not currently active) Ted Mielczarek]

The updated URL contains a demo that reproduces the problem. I just tested with my (slightly-out-of-date) 20101113 nightly and can still reproduce the problem.

(The author said he lost the contents of the blog post to a system crash, but this demo is still there.)

Comment 7

[David Mandelin [:dmandelin]]

I tried again with the new site, and it definitely doesn't work as desired, but I don't get the same behavior as Ted. Instead, it's just pretty laggy as I drag. xperf says our time in this is 18% JS, 15% XUL, 23% nvwgf2um.dll (nvid driver file, apparently), and 27% various Windows graphics dlls, principally d2d1.dll and d3d10_1core.dll.

That, plus the fact that this is Windows-only and we don't recall ever seeing a platform-specific JS-related perf issue of this type, says to me that this is more likely graphics than JS.