Closed Bug 87165 Opened 24 years ago Closed 1 year ago

javascript is very slow for this example

Categories

(Core :: DOM: Core & HTML, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: bmd, Unassigned)

References

()

Details

(Keywords: perf, testcase)

Attachments

(4 files)

I've got some heiarchial menu code written in javascript that works fine with IE and NS 4.XX but takes forever to render with mozilla. During the rendering time, mozilla sits at 100% cpu usage.
Some more info, it seems that this bug get's triggered more often when the page is already cached, so if you clicked on the html attachment and nothing happened, try it again, or try the back/forward button a few times to re-render it. I'm getting brave here, so I'm gonna slap the 4xp keyword on this thing since it works with the Netscape 4.76 on Linux that I've tested. Sorry if I have the wong component.
Keywords: 4xp
confirmed WinXP/20010619 adding perf keyword Platform/OS->All
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: perf
OS: Linux → All
Hardware: PC → All
Status: NEW → ASSIGNED
Blocks: 91351
I downloaded the test case and meaqsured the time needed for complete rendering of the screen, after hitting the first arrow: NS4.7: 1.6 sec, checkboxes are not displayed Moz 04-29-2001: 1.1 sec Moz 0.9.5: 1.3 sec, no visual problems Moz 2001102503: 1.1 sec, no visual problems IE5.5: 0.7 sec, no visual problems system spec: Win98, K6-III/400, 192MB ram.
Blocks: 21762
Keywords: testcase
Just an FYI, the first attachment is a .zip file that contains a more usable testcase than the second example.
Also note that it's not slow if you run it off of local disk (IE: using a file:// url). The testcase has to be delivered by a remote webserver.
Attachment #39558 - Attachment mime type: application/octet-stream → application/x-zip-compressed
Mass-reassigning bugs to dom_bugs@netscape.com
Assignee: jst → dom_bugs
Status: ASSIGNED → NEW
Attachment #39558 - Attachment mime type: application/x-zip-compressed → application/zip
Is this still an issue? I'm not seeing any slowness on those testcases....
OK, I can reproduce the slowness, depending on my cookie settings. The getCurrState() function seems to do this really slow walk over the cookie string, and it's called a lot. So doubling the length of the cookie string doubles the execution time of this code....
I can still reproduce this with latest Fx3b5pre on WinXP. Clicking on a category takes some time comparing to IE7 and uses 40% of CPU comparing to 4-6% in IE7
Are your cookies exactly identical in the different browsers?
Assignee: general → nobody
QA Contact: desale → general
Build ID: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b13pre) Gecko/20110303 Firefox/4.0b13pre WFM. Compared with both IE 8 and Chrome. Note that this bug was originally comparing the performance of Mozilla with NS 4 and IE 5.5.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
José Jeria, I assume you tested with various cookie settings, etc? See comment 12.
(In reply to comment #16) > I assume you tested with various cookie settings, etc? See comment > 12. No sorry.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Brian, have you tried testing with the latest version of Firefox?

Bulk-downgrade of unassigned, untouched DOM/Storage bug's priority.

If you have reason to believe, this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5

I'm not seeing any slowness on those testcases. Given there has been a lot of code changes and performance improvements on Gecko since the bug was reported, I am going to close this. Please open a new bug when you encounter a related issue; attaching a profile is always a huge help. Thank you.

Status: REOPENED → RESOLVED
Closed: 14 years ago1 year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: