Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Докладніше

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

High Memory usage by js (1,075.75 MB)

  • 1 відповідь
  • 17 мають цю проблему
  • 2 перегляди
  • Остання відповідь від scoobidiver

more options

about:memory shows high memory usage (over a gig) by js, which I assume is javascript. The referenced page seems to be my iGoogle homepage. Could that really be eating up this much memory? Readout below:

2,148.23 MB (100.0%) -- explicit

├──1,075.75 MB (50.08%) -- js
│  ├────755.75 MB (35.18%) -- compartment(https://plusone.google.com/u/0/_/+1/fastbutton?url=http%3A%2F%2Frss.slashdot.org%2F%257Er%2FSlashdot%2Fslashdot%2F%257E3%2F5Z-KNyWbLx0%2Fmit-tetris-hack-source-code-released&size=small&count=true&source=google%3Aigoogle&hl=en&jsh=m%3B%2F_%2Fapps-static%2F_%2Fjs%2Fwidget%2F__features__%2Frt%3Dj%2Fver%3DSvSTGk8PZnM.en.%2Fsv%3D1%2Fam%3D!K2t8zmDaIyaNjPbXTQ%2Fd%3D1%2F#id=I1_1335941403316&parent=http%3A%2F%2Fwww.google.com&rpctoken=823030084&_methods=onPlusOne%2C_ready%2C_close%2C_open%2C_resizeMe%2C_renderstart)
│  │    ├──401.29 MB (18.68%) -- gc-heap
│  │    │  ├──158.41 MB (07.37%) -- objects
│  │    │  │  ├───93.14 MB (04.34%) ── non-function
│  │    │  │  └───65.27 MB (03.04%) ── function
│  │    │  ├──117.55 MB (05.47%) ── scripts
│  │    │  ├───97.74 MB (04.55%) -- shapes
│  │    │  │   ├──44.60 MB (02.08%) ── dict
│  │    │  │   ├──40.96 MB (01.91%) ── tree
│  │    │  │   └──12.17 MB (00.57%) ── base
│  │    │  └───27.58 MB (01.28%) ++ (3 tiny)
│  │    ├──246.07 MB (11.45%) ── script-data
│  │    ├───44.45 MB (02.07%) ++ shapes-extra
│  │    ├───36.42 MB (01.70%) -- objects
│  │    │   ├──34.82 MB (01.62%) ── slots
│  │    │   └───1.60 MB (00.07%) ++ (2 tiny)
│  │    ├───23.64 MB (01.10%) ++ type-inference
│  │    └────3.89 MB (00.18%) ++ (3 tiny)
│  ├────139.49 MB (06.49%) ++ (50 tiny)
│  ├─────77.43 MB (03.60%) -- 
compartment(http://www.google.com/ig)
│  │     ├──50.20 MB (02.34%) -- gc-heap
│  │     │  ├──27.67 MB (01.29%) ++ (5 tiny)
│  │     │  └──22.53 MB (01.05%) ++ shapes
│  │     └──27.23 MB (01.27%) ++ (7 tiny)
│  ├─────73.06 MB (03.40%) -- compartment([System 
Principal], 0x558a000)
│  │     ├──40.51 MB (01.89%) ++ gc-heap
│  │     └──32.55 MB (01.52%) ++ (7 tiny)
│  └─────30.02 MB (01.40%) ── gc-heap-decommitted
├────665.52 MB (30.98%) -- images
│    ├──665.08 MB (30.96%) -- content
│    │  ├──665.08 MB (30.96%) -- used
│    │  │  ├──600.88 MB (27.97%) ── uncompressed-heap
│    │  │  ├───64.20 MB (02.99%) ── raw
│    │  │  └────0.00 MB (00.00%) ── uncompressed-nonheap
│    │  └────0.00 MB (00.00%) ++ unused
│    └────0.44 MB (00.02%) ++ chrome
├────270.48 MB (12.59%) ── heap-unclassified
├─────73.65 MB (03.43%) -- window-objects
│     ├──72.35 MB (03.37%) ++ active
│     └───1.30 MB (00.06%) ++ other
├─────26.96 MB (01.26%) ── network-memory-cache
├─────25.92 MB (01.21%) -- storage
│     ├──23.95 MB (01.11%) ++ sqlite
│     └───1.98 MB (00.09%) ++ prefixset
└──────9.94 MB (00.46%) ++ (7 tiny)
about:memory shows high memory usage (over a gig) by js, which I assume is javascript. The referenced page seems to be my iGoogle homepage. Could that really be eating up this much memory? Readout below:<br /> <br /> <pre><nowiki>2,148.23 MB (100.0%) -- explicit ├──1,075.75 MB (50.08%) -- js │ ├────755.75 MB (35.18%) -- compartment(https://plusone.google.com/u/0/_/+1/fastbutton?url=http%3A%2F%2Frss.slashdot.org%2F%257Er%2FSlashdot%2Fslashdot%2F%257E3%2F5Z-KNyWbLx0%2Fmit-tetris-hack-source-code-released&size=small&count=true&source=google%3Aigoogle&hl=en&jsh=m%3B%2F_%2Fapps-static%2F_%2Fjs%2Fwidget%2F__features__%2Frt%3Dj%2Fver%3DSvSTGk8PZnM.en.%2Fsv%3D1%2Fam%3D!K2t8zmDaIyaNjPbXTQ%2Fd%3D1%2F#id=I1_1335941403316&parent=http%3A%2F%2Fwww.google.com&rpctoken=823030084&_methods=onPlusOne%2C_ready%2C_close%2C_open%2C_resizeMe%2C_renderstart) │ │ ├──401.29 MB (18.68%) -- gc-heap │ │ │ ├──158.41 MB (07.37%) -- objects │ │ │ │ ├───93.14 MB (04.34%) ── non-function │ │ │ │ └───65.27 MB (03.04%) ── function │ │ │ ├──117.55 MB (05.47%) ── scripts │ │ │ ├───97.74 MB (04.55%) -- shapes │ │ │ │ ├──44.60 MB (02.08%) ── dict │ │ │ │ ├──40.96 MB (01.91%) ── tree │ │ │ │ └──12.17 MB (00.57%) ── base │ │ │ └───27.58 MB (01.28%) ++ (3 tiny) │ │ ├──246.07 MB (11.45%) ── script-data │ │ ├───44.45 MB (02.07%) ++ shapes-extra │ │ ├───36.42 MB (01.70%) -- objects │ │ │ ├──34.82 MB (01.62%) ── slots │ │ │ └───1.60 MB (00.07%) ++ (2 tiny) │ │ ├───23.64 MB (01.10%) ++ type-inference │ │ └────3.89 MB (00.18%) ++ (3 tiny) │ ├────139.49 MB (06.49%) ++ (50 tiny) │ ├─────77.43 MB (03.60%) -- compartment(http://www.google.com/ig) │ │ ├──50.20 MB (02.34%) -- gc-heap │ │ │ ├──27.67 MB (01.29%) ++ (5 tiny) │ │ │ └──22.53 MB (01.05%) ++ shapes │ │ └──27.23 MB (01.27%) ++ (7 tiny) │ ├─────73.06 MB (03.40%) -- compartment([System Principal], 0x558a000) │ │ ├──40.51 MB (01.89%) ++ gc-heap │ │ └──32.55 MB (01.52%) ++ (7 tiny) │ └─────30.02 MB (01.40%) ── gc-heap-decommitted ├────665.52 MB (30.98%) -- images │ ├──665.08 MB (30.96%) -- content │ │ ├──665.08 MB (30.96%) -- used │ │ │ ├──600.88 MB (27.97%) ── uncompressed-heap │ │ │ ├───64.20 MB (02.99%) ── raw │ │ │ └────0.00 MB (00.00%) ── uncompressed-nonheap │ │ └────0.00 MB (00.00%) ++ unused │ └────0.44 MB (00.02%) ++ chrome ├────270.48 MB (12.59%) ── heap-unclassified ├─────73.65 MB (03.43%) -- window-objects │ ├──72.35 MB (03.37%) ++ active │ └───1.30 MB (00.06%) ++ other ├─────26.96 MB (01.26%) ── network-memory-cache ├─────25.92 MB (01.21%) -- storage │ ├──23.95 MB (01.11%) ++ sqlite │ └───1.98 MB (00.09%) ++ prefixset └──────9.94 MB (00.46%) ++ (7 tiny)</nowiki></pre>

Змінено cor-el

Усі відповіді (1)

more options

The MemShrink project driven by Mozilla aims to reduce memory usage in each new release.

If you want to reduce it in your current version, you can try some solutions from the Firefox uses too much memory or CPU resources - How to fix article.