240440 - memory leak in X when opening javascript cosole

Status: RESOLVED EXPIRED

(Toolkit Graveyard :: Error Console, defect)

Description

[Franz Pletz]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040409 Firefox/0.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040409 Firefox/0.8

When I open the javascript console for debugging purposes (icon shows an error),
I have no more control over X. Over SSH I can watch X consuming more and more
memory until it finally crashes.

Reproducible: Always
Steps to Reproduce:
1. Start Firefox
2. Open (any) document with JavaScript errors (icon)
3. Open javascript console

Actual Results:  
No more control over X, it consumes more and more memory -> memory leak.

Expected Results:  
Open the javascript console.

I've got no more information because over lockup of X, the console ist unusable.

Comment 1

[Mike Connor [:mconnor]]

what about on a current nightly build?  I know there's been a lot of work on
leaks since 0.8/1.6

Comment 2

[Rob Hagemans]

> When I open the javascript console for debugging purposes (icon shows an error),
> I have no more control over X. Over SSH I can watch X consuming more and more
> memory until it finally crashes.

I have a similar issue, always when I open Wikipedia.org, also with the latest
Firefox 0.8 nightly build on a i686 Linux system. When Firefox opens
wikipedia.org, the memory usage grows until all memory is used. Sometimes it
survives and becomes usable after a while (although the memory remains in use
until I quit Firefox), sometimes X crashes.

Comment 3

[Rob Hagemans]

I have zoomed in a bit on my issue and it might be not quite related. it seems
to have to do with Unicode support. Lines that are in Malayalam and those in
Tamil trigger the memory leak. For instance a html file containing just the
symbol த does it, while a lot of other Unicode symbols do not.

Comment 4

[Robin Monks]

I'm moving to JavaScript Console...

Comment 5

[Nickolay_Ponomarev]

Can you reproduce this with a recent trunk build?

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.