[INVALID] A big bug in NoScript or I'm doing some stupidity?

[farluiz]

Please, someone can test the following page for me:

a) Enter into the following page (URL below) with all scripts DISABLED;

http://esporte.uol.com.br/futebol/ultim ... acabou.htm

b) Only wait! No need to do anything! Firefox begins to crazily allocate memory, memory, memory, turns slowly, slowly and crashes.

With scripts in the page above ENABLED, everything goes ok.

I'm crazy? I'm doing some stupidity?

My machine:
Pentium 4 with 2GB memory
WINDOWS XP SP3 with all fixes and all .net
FIREFOX 12.0
NOSCRIT 2.4.3

[dhouwn]

When scripts are disabled, this page's memory consumptions differs a lot of in terms of whether you have images allowed or not, without images it peaks at 80 MB, with at nearly 2 GB for me.

Seems like all images are decoded when JS is disabled, that's why there is the memory peak.

Bad page design.

[farluiz]

Thank you by your reply. In my machine this page "shutdown" Firefox in a few minutes with JS disabled and with no user interaction. Crazy, no?

[dhouwn]

Virtual address space exhaustion. Firefox on 32-bit XP can only use up to 2GiB (unless you set the /3GB kernel switch).
Apparently https://bugzil.la/670967 is not helping.

image.mem.decodeondraw (which is now enabled per default) should help until you scroll down to the images.

[therube]

Could you post that link again (in URL tags) as the board looks to have corrupted it.

[therube]

> this page "shutdown" Firefox in a few minutes

Crashed me too on XP, 2GB RAM.


Just to be clear, this has nothing to do with NoScript.
(If you remove NoScript & manually disable JavaScript, you will observe the same.)

Not sure just what image.mem.decodeondraw is doing?
From here, Bug 666560 - The best way to handle images, it was neat to load the page in question, observe Mem go up to ~1.4GB, then move to some other tabs & at some point Mem declined to ~300MB (in my case). Jump back to the gcforum.org tab & Mem shoots right back up.

[dhouwn]

Not sure just what image.mem.decodeondraw is doing?

Images will not be decoded (converted from compressed format, e.g. JPEG into simple bits per pixel, that's what causes the memory peak) until what they are on is drawn (note that is not the same as them being visible like I thought at first, that's why there is bug https://bugzil.la/689623 I guess).

[therube]

Link:

Code: Select all

http://esporte.uol.com.br/futebol/ultimas-noticias/2012/05/31/joel-santana-revela-surpresa-com-novela-ronaldinho-no-fla-e-decreta-acabou.htm

Crash, 0d68ec07-07af-4dd0-a6cb-7159d2120601.
Related, Bug 760952 - crash in nsLineLayout::ReflowFrame.

Been months since my last crash (& this one was was purposely forced) & I see they now log various memory related parameters, which they did not have before.

until what they are on is drawn

Explain?
Is that once the page itself is loaded, has focus?

[GµårÐïåñ]

http://esporte.uol.com.br/futebol/ultim ... acabou.htm

Next time wrap your links in between [URL] tags so they are not chomped up like this.

[therube]

> Next time...

That actually happened after the fact.
Originally it did display correctly. Don't know if he went back & mod'd the link or what?

[farluiz]

Link:

Code: Select all

http://esporte.uol.com.br/futebol/ultimas-noticias/2012/05/31/joel-santana-revela-surpresa-com-novela-ronaldinho-no-fla-e-decreta-acabou.htm

Crash, 0d68ec07-07af-4dd0-a6cb-7159d2120601.
Related, Bug 760952 - crash in nsLineLayout::ReflowFrame.

Been months since my last crash (& this one was was purposely forced) & I see they now log various memory related parameters, which they did not have before.

until what they are on is drawn

Explain?
Is that once the page itself is loaded, has focus?

Thank you for reporting that bug to Mozilla. I survey bugzilla in the last days and I read a lot of complaints about Firefox and pages with many images. Even in OS's other than Windows, Firefox becomes "drunk" after a simple visit to such pages.

Reading the "talks" between Mozilla's engineers, I am convinced that there is a terrible project flaw in Firefox about images manipulation.

I hope be wrong because I love Firefox, but I see shadows in the Firefox future!

Thank you all again!
Farluiz

[dhouwn]

Don't know if he went back & mod'd the link or what?

Might have happened when the title got edited?

[GµårÐïåñ]

It only happens if its a long URL and not wrapped and if it was wrapped in URL tags, no matter how many times you edit it, it would not change or mangle like that. Simple as that. It happened, its been noted, let's call it a day.

[dhouwn]

It only happens if its a long URL and not wrapped and if it was wrapped in URL tags, no matter how many times you edit it, it would not change or mangle like that.

Just to reiterate: if it's not wrapped in URL tags then it happens after the first edit? Because at first the link was certainly fine.

[therube]

> at first the link was certainly fine

Right.

Below being posted without Preview, simply Submit.
Further I will not edit this post a million times as I am apt to do .
Lets see what happens ...

http://esporte.uol.com.br/futebol/ultim ... acabou.htm