75933 - Mozilla temporarily freezes on bug lists

Status: RESOLVED WORKSFORME

(Core :: Layout, defect)

Description

[Eric Vaandering (no email)]

When entering a search on bugzilla that generates a fairly long list (say search
on bugzilla in the URL), mozilla freezes for a while.

As things are loading, mozilla is not responsive. When all the content is
present, it is responsive again. Then it freezes up again. With the above
example on a dual 450 MHz linux box, the second freeze is about 15-20 seconds.

After this, everything is fine.

I think I notice this at other URLs too.

Try moving the scroll bars to see if the browser is responsive.

Comment 1

[Asa Dotzler [:asa]]

I've seen this since last week on win32.  The CPU goes up to 100% for between 10
and 30 seconds when laying out the buglist page.  Sometimes it doesnt happen
until I begin to scroll the list.

Comment 2

[Eric Vaandering (no email)]

Probably a dup of bug 77460

Comment 3

[Jesse Ruderman]

The second freeze is bug 77460.

Comment 4

[S A Jarrett-Sprague]

I am getting this with mozilla 0.9.3 build 2001080104. I don't seem to be
experiencing it at ximian's bugzilla page but I do at gnome's bugzilla (badly).
With gnome's bugzilla I experence the problem when I select a product to report
a bug. At this point I cant scroll on any of the pull down menus and the whole
of mozilla does't respond. Following a period of time it unfreezes.


I also note that the page seems to be rendered properly at first and then all
the boxes and pull downs get screwed up before sorting itself out again. 

Comment 5

[karnaze (gone)]

Reassigning to attinasi.

Comment 6

[Fabian Schach]

2002022603

I think I don't see this anymore in builds during the last weeks. Can anyone
with a not so fast ;-) computer test this?

As a testcase I used
http://bugzilla.mozilla.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED

While loading the list I didn't encounter a freeze.

Comment 7

[Eric Vaandering (no email)]

I don't see this either with my 266 MHz Pentium machine.

Would like to resolve this bug. Should things like this were the bug seems to
have been fixed but its not known how be marked "FIXED" or "WORKSFORME?"

Comment 8

[Eric Vaandering (no email)]

Marking works for me. No problems here with 0.9.9 or RC1