Performance problem after some time at this webpage

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
13 years ago
9 years ago

People

(Reporter: pschleritzko, Unassigned)

Tracking

1.5.0.x Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 5-15-2010], URL)

Attachments

(1 attachment)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8) Gecko/20051111 Firefox/1.5

when you use this site (http://www.epos4.at) longer than 15 minutes, firefox.exe uses about 350mb of memory. i think that should not be. working is no longer good!

Reproducible: Always

Steps to Reproduce:
1. goto http://www.epos4.at
2. create account and login
3. stay about 15 to 20 minutes

Actual Results:  
the mem-usage increased and the computer-performance slows down

Expected Results:  
use less memory

i had 3 tabs open, and no other processes
(Reporter)

Comment 1

13 years ago
Created attachment 205034 [details]
here you can see the performance leek
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode
Whiteboard: [CLOSEME 5-15-2010]
Version: unspecified → 1.5.0.x Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.