לאתר זה תהיה פונקציונליות מוגבלת בזמן שאנו מתחזקים אותו לשיפור החוויה שלך. אם מאמר מסויים לא פותר את הבעיה שלך וברצונך לשאול שאלה, קהילת התמיכה שלנו מחכה לעזור לך ב־Twitter תחת ‎@FirefoxSupport וב־Reddit תחת ‎/r/firefox.

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

Upgrading to FF 27 created huge (~1 GB/hr) memory usage for iconified windows on Mac 10.8

  • 1 תגובה
  • 17 have this problem
  • 4 views
  • תגובה אחרונה מאת Wesley Branton

more options

Here is what I know about the problem:

- Two different Macs (10.8.x, 10.9.x) with 32 GB RAM ran out of system swap due to the size of the Firefox process growing to over 20 GB, and both machines had virtually idle CPUs with no Firefox usage whatsoever - they were unattended - It occurred immediately after upgrading from Firefox 26 to 27.0.1 - The set of pages, tabs, windows was the same before and after upgrading - There does not seem to be a single identifiable URL that causes the problem, but opening a window with this URL and then iconifying it causes memory to be leaked at a substantial rate (at least on one OS X 10.8.5 machine)

 - http://msdn.microsoft.com/en-us/magazine/cc163744.aspx

- I normally have ~25 tabs distributed across ~8 windows, all of which but one are iconified - Memory is consumed at the staggering rate of ~1 GB/hour while the offensive window is iconified - Memory is not leaked per-se - about:memory confirms that heap-unclassified memory is growing rapidly, but as soon as the offending window is opened and no longer iconified, the memory usage immediately drops back to the normal ~1 GB or so - this is also verifiable in Activity Monitor.app, etc - The problem occurs in safe mode, but regardless the only plugins installed are Shockwave Flash, QuickTime, and Java Applet - I have killed Firefox repeatedly and can recreate the same memory usage pattern - I have at least one Mac, however, on which trying to reproduce this does nothing - I've already spent hours trying to determine even the initial cause of this

Here is what I know about the problem: - Two different Macs (10.8.x, 10.9.x) with 32 GB RAM ran out of system swap due to the size of the Firefox process growing to over 20 GB, and both machines had virtually idle CPUs with no Firefox usage whatsoever - they were unattended - It occurred immediately after upgrading from Firefox 26 to 27.0.1 - The set of pages, tabs, windows was the same before and after upgrading - There does not seem to be a single identifiable URL that causes the problem, but opening a window with this URL and then iconifying it causes memory to be leaked at a substantial rate (at least on one OS X 10.8.5 machine) - http://msdn.microsoft.com/en-us/magazine/cc163744.aspx - I normally have ~25 tabs distributed across ~8 windows, all of which but one are iconified - Memory is consumed at the staggering rate of ~1 GB/hour while the offensive window is iconified - Memory is not leaked per-se - about:memory confirms that heap-unclassified memory is growing rapidly, but as soon as the offending window is opened and no longer iconified, the memory usage immediately drops back to the normal ~1 GB or so - this is also verifiable in Activity Monitor.app, etc - The problem occurs in safe mode, but regardless the only plugins installed are Shockwave Flash, QuickTime, and Java Applet - I have killed Firefox repeatedly and can recreate the same memory usage pattern - I have at least one Mac, however, on which trying to reproduce this does nothing - I've already spent hours trying to determine even the initial cause of this

כל התגובות (1)

more options

Another user was talking about this issue on the forum and created a bug report.

You can create another bug report or add your details into this report.