Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Since upgrading to 3.6.10 it appears that there is a memory leak. The browser becomes unuseable until I shut it down and restart. I have tried bookmarking my tabs in the 6 windows which I generally run but ... Any ideas on how to trouble shoot? Thanks

  • 2 trả lời
  • 75 gặp vấn đề này
  • 1 lượt xem
  • Trả lời mới nhất được viết bởi mig

more options

Firefox 3.6.10 under Mac OS X 10.6.4 with a Mac Pro (Tower of Power) 2 - 3.0 GHz dual core Xeons, 5 GB RAM. Firefox takes up to 1 GB of memory and CPU usage goes over 100% in the Activity Monitor.

Firefox 3.6.10 under Mac OS X 10.6.4 with a Mac Pro (Tower of Power) 2 - 3.0 GHz dual core Xeons, 5 GB RAM. Firefox takes up to 1 GB of memory and CPU usage goes over 100% in the Activity Monitor.

Tất cả các câu trả lời (2)

more options

I've recently downloaded 4.0 beta. Works much better than the patched 3.6.10 which becomes unusable. I have loaded up the 4.0 Beta browser with the same number of Windows and Tabs which could reproduce the original problem. Viewing under the Mac OS Activity Monitor while there might still be a memory leak, I believe that the largest problem seems to be a thread that has taken over the CPU(s) and not relinquishing control. When the problem would occur the CPU Usage would go over 100% with the 4.0 Beta it is only at 12%. Memory usage ranges from over 1 GB with 3.6.10 to 650 MB with the 4.0 Beta. I did clear out my download list and the browsing content could account for the differences in memory usage. Hope that this helps.

-- mig

more options

I believe that this issue has been resolved by upgrading the Adobe flash plugin to version 10.1.85.3.