Closed Bug 272338 Opened 21 years ago Closed 20 years ago

After using google images for a while, browser slows to a crawl

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: theosib, Unassigned)

References

(
URL
)

Details

(Keywords: perf)

User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux 2.6.9-gentoo-r1) (KHTML, like Gecko) Build Identifier: This is a very consistent occurrence. Go to images.google.com and start searching for images. Click on a few search results, view the images, etc. Then close the window or tab for google. Immediately or shortly thereafter, Mozilla becomes unusably slow. This includes clicking on links, clicking the back button, selecting drop-down menus (File, Edit, etc.), scrolling a window, or typing in an edit field. I'm using KDE with multiple desktops, and when I switch back to the desktop with Mozilla, it takes roughly 6 seconds for the screen to repaint. Everything else on the system is just as zippy as ever (Athlon 2800+, Radeon 9000). When idle, Mozilla doesn't appear to be using much CPU time, but when I try to make Mozilla DO anything, the CPU meter spikes to 100% the entire time it's processing. In order to make the problem go away, I have to completely close out all Mozilla windows. When I restart it, Mozilla is fast again. Reproducible: Always Steps to Reproduce: 1. Open some browser windows. 2. Go to images.google.com, search, and browse some images 3. Close the google window Actual Results: Mozilla becomes unusably slow Expected Results: Mozilla should not become unusably slow. I'm using a Gentoo ebuild of Mozilla.
how much RAM do you have? home much memory was Mozilla using?
and what does about:cache look like when this is happening?
Sorry I haven't responded yet, but now that I'm trying to make the problem happen again, it won't. You know how it is. Anyhow, I have 1 gig of RAM. I didn't check how much RAM Mozilla was using when I originally was experiencing the problem, but I do recall that it wasn't hitting swap. In fact, swap wasn't being used at all.
what version of Mozilla are you using?
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040919
It finally started acting up again. This is what I see in 'top': PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10318 root 15 0 192m 114m 81m S 5.0 11.3 104:19.79 X 10545 tim 15 0 130m 112m 43m S 1.0 11.2 59:41.58 kdeinit 10591 tim 15 0 77396 55m 36m S 0.0 5.5 28:47.13 mozilla-bin 10607 tim 16 0 77396 55m 36m S 0.0 5.5 0:00.07 mozilla-bin 10608 tim 16 0 77396 55m 36m S 0.0 5.5 0:03.01 mozilla-bin 10656 tim 15 0 77396 55m 36m S 0.0 5.5 0:04.63 mozilla-bin 19527 tim 16 0 77396 55m 36m S 0.0 5.5 0:00.00 mozilla-bin ... Here's about:cache Memory cache device Number of entries: 1771 Maximum storage size: 31744 KiB Storage in use: 31669 KiB Inactive storage: 27847 KiB List Cache Entries Disk cache device Number of entries: 2908 Maximum storage size: 51200 KiB Storage in use: 21397 KiB Cache Directory: /home/tim/.mozilla/default/fyweqa9y.slt/Cache List Cache Entries I clicked on one of the "List Cache Entries" links, and then Mozilla froze up completely.
that looks mostly normal. Mozilla stores the cached images on the X server, so X memory usage is high, but with 1 GB, it should be fine. If you're sure the hang you saw was a real hang (not just Mozilla taking a long time) you should file a new bug for that.
Keywords: perf
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.