597838 - reproducible hang in xul trees when resizing to ~minwidth (tested winxp, win7) [@ hang | nsViewManager::ProcessPendingUpdates]

Status: NEW

(Core :: Web Painting, defect)

Description

[Giorgio]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b6pre) Gecko/20100908 Firefox/4.0b6pre
Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b6pre) Gecko/20100908 Firefox/4.0b6pre

hi, probably it's a windows issue, and xp and seven(aero) both are tested affected

when a xul tree is resized near to its min-width when the horizontal scrollbar buttons appears the windows crashes

run the xul file and resize the window in width to reproduce it

thank you

Reproducible: Always

Comment 1

[Giorgio]

Attachment: test case/bug demo

Comment 2

[Giorgio]

p.s. you must run it in xulrunner!

Comment 3

[Benjamin Smedberg]

It's a bug, but not a blocker.

Comment 4

[Robert Utasi [:hunboy]]

Attachment: an other testcase with splitter (xul)

reproducible always only on the trunk. freeze happens randomly when the unnessesary horizontal scrollbar shows up. (that shows up on previous versions also, but not freeze)

Comment 5

[timeless]

https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg
please install the 32bit version of windbg.

Comment 6

[Hicham]

I have chatzilla freezing on xulrunner-2.0b8 when resizing the user list to 0.

Host OS : Fedora rawhide i686

Comment 7

[Robert Utasi [:hunboy]]

Attachment: stacktrace

Comment 8

[timeless]

robert: i was expecting an access violation, your stack just shows you manually broke into the process.

if it's indeed a hang, you should run:

!analyze -v -hang

as the final step

Comment 9

[Robert Utasi [:hunboy]]

the first trunk where happens: [XULRunner 2.0b4pre/20100813033105]
the last trunk where not: the splitter goes crazy (it supposed to be a bugfix
for that)

timeless: i'll do that today a little bit of later.

Comment 10

[Robert Utasi [:hunboy]]

Attachment: stacktrace with -hang

yes its a hang with 100% core usage

Comment 11

[BugBot [:suhaib / :marco]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Comment 12

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:tnikkel, could you have a look please?

For more information, please visit BugBot documentation.

Comment 13

[Timothy Nikkel (:tnikkel)]

Would love to stop getting nagged about bugs that haven't been touched in a decade by bugbot.

Comment 14

[Suhaib Mujahid [:suhaib]]

This is part of the process of migrating bugs to the new severity system, see comment 11.