Re: Hovering mouse over tab X button causes 100% CPU usage in Linux

paul <[email protected]> Sun, 22 Jun 2008 18:34:36 -0500
Newsgroups gmane.comp.mozilla.multizilla
Organization The Mozdev Foundation - news server
Message-ID <[email protected]>
Yves Lambert wrote:
> paul wrote:
>>> I don't have any javascript debugger in my seamonkey. Probably because I
>>> compiled without composer, mail, irc etc (browser only). I'll re-compile
>>> with default options (full suite) and see what I can find. Thanks.
>>>
>>> Paul
>>>     
>>
>> Well after recompiling seamonkey I still can't find it on the menu. How
>> do I start the javascript debugger?
> 
> Now I am no more sure that you'd find something interesting.
> I made a mistake, I meant the error console not the debugger - I did not
> see Vincent's message and I do not experiment the problem with this
> Build identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13)
> Gecko/20080313 MultiZilla/1.8.3.2g Mnenhy/0.7.5.0
> 
> As Vincent and you experiment the problem and i do not, i assume that
> the problem (if it is consistant) may be due to a seamonkey bug. By the
> way, javascript debugger would help to find out what bugs.
> 
> .
> 
> If I understand http://books.mozdev.org/html/mozilla-app-b-sect-5.html
> there is no menu item and you have to launch seamonkey with '-venkman'
> as parameter
> "Invoke the -venkman command-line argument by typing *mozilla -venkman*
> to start Mozilla."

Thanks for the hint. It seems my guess about composer/mail/irc has
nothing to do with it. I missed another option about developer tools...
so I'm compiling again. :)

BTW the error console shows nothing (no errors, no warnings).

I'm using this seamonkey:

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.13) Gecko/20080621
MultiZilla/1.8.3.4e SeaMonkey/1.1.9

So it seems you and I are using the same seamonkey (but mine is 64-bit,
yours 32-bit) and I'm using a newer build of multizilla.

I am using the kernel 2.6.25, X.org 7.3 and nvidia video driver
173.14.09. I'm using KDE 3.5.9 as my desktop environment but the same
problem occurred in Gnome and XFCE when I tried them.

Thanks,
Paul