147128 - Menus/buttons stop responding in browser

Status: RESOLVED WORKSFORME

(SeaMonkey :: UI Design, defect)

Description

[Matt Fago]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc3) Gecko/20020523
BuildID:    2002052309

After a while (not 100% reproducable) the menus and buttons stop responding in
the browser. Not all windows are affected, so it is possible to quit and
restart. Nevertheless, this is very annoying.

Reproducible: Sometimes
Steps to Reproduce:
1.Browse for long enough.
2.Try to use manu/button.
3.

Actual Results:  Nothing works

Expected Results:  Menus/buttons work

SuSE linux 8.0 with KDE 3.0.1. Is is related to this? I have no easy way to test.

Comment 1

[Balázs Nagykékesi]

I have experienced the same thing.
I have encountered with it today but I did not have to browse for a long time
for this bug to appear.

I was able to reproduce this bug anyway. Just push the arrow next to menubar so
the menus' title is not visible. Quit the browser. Restart the browser and now I
can't access some menus. With time more and more menus becomes disabled. Once I
had only  the help menu accessible.

I have PC and Windows so it is not only on Linux.

Comment 2

[Kai Lahmann (is there, where MNG is)]

WFM with trunk 2002073022, linux. reporter (Matt Fago): can you reproduce this
bug with a recent build of mozilla (for example, 1.1beta)? if so, please comment
again with details. if not, please resolve this bug as WORKSFORME. thanks.

Comment 3

[Matt Fago]

I have not had this happen since switching to 1.1beta (2002072204) on linux. It
was sporadic though.

I've also upgraded to KDE 3.0.2. Perhaps kde 3.0.0 was causing the bug for me,
but I am not in a position to check 1.1beta with KDE 3.0.0.

So I'm marking WORKSFORME, and someone can reopen if it shows up again.

Comment 4

[Matt Fago]

Sorry, just had this happen to me again. This is in 2002072204 (1.1 beta), with
KDE 3.0.2. Haven't been able to test in a nightly (I'll try with a nightly
tomorrow).

It is very intermittent, but once it happens you're SOL -- 'mise well be a crash.

Note that you cannot even close a browser window (much less use any of Mozilla's
widgets). This sounds fishy to me.

Anyone else seen this on Linux?

Comment 5

[Kenneth Herron]

Matt,

The behavior you're describing sounds like what happens when using the
javascript debugger and single-stepping through a javascript function. While the
JS interpreter is halted, most of the controls in the relevant window become
nonfunctional. 

Most of the mozilla user interface is implemented through javascript; click a
button and a little JS function somewhere executes. It's possible that you're
triggering something which makes the JS engine for that window halt.

If you can get this to happen again, please try to open the JS console (Tools->
Web Development-> Javascript console) and see if there are any interesting
messages there. (The JS console usually fills up with junk from normal surfing,
so it can be hard to tell what messages are recent, but please see what you can do.)

Comment 6

[Kenneth Herron]

Matt, are you continuing to experience this problem?

Comment 7

[Matt Fago]

Has not happened for quite a while. I suppose you could mark as WORKSFORME.

Comment 8

[Alexander Opitz]

mark as WFM as of last comment of the reporter.