F5F Stay Refreshed Software Operating Systems Discuss high memory consumption on the LTT forum.

Discuss high memory consumption on the LTT forum.

Discuss high memory consumption on the LTT forum.

Pages (2): Previous 1 2
_
_Keira
Member
100
05-27-2016, 07:34 AM
#11
You're seeing a file size of roughly 200MB to 500MB.
_
_Keira
05-27-2016, 07:34 AM #11

You're seeing a file size of roughly 200MB to 500MB.

M
mmillaa
Member
197
05-29-2016, 02:56 AM
#12
You're seeing around 1GB of data usage.
M
mmillaa
05-29-2016, 02:56 AM #12

You're seeing around 1GB of data usage.

F
Fantatrol_HD
Member
64
05-29-2016, 04:36 AM
#13
So am I.
F
Fantatrol_HD
05-29-2016, 04:36 AM #13

So am I.

D
Dominik_SK
Member
238
06-07-2016, 01:27 AM
#14
You're on a 32-bit system, which is unusual since most people use 64-bit. It seems like this issue isn't common, just something you encountered alone.
D
Dominik_SK
06-07-2016, 01:27 AM #14

You're on a 32-bit system, which is unusual since most people use 64-bit. It seems like this issue isn't common, just something you encountered alone.

X
xAlphaLegend
Member
222
06-07-2016, 07:54 AM
#15
I used to be frustrated by this. I consistently reach a minimum of 900MB in usage when it's left running. On a 4GB device, this puts me very close to failure.
X
xAlphaLegend
06-07-2016, 07:54 AM #15

I used to be frustrated by this. I consistently reach a minimum of 900MB in usage when it's left running. On a 4GB device, this puts me very close to failure.

K
KochJus7in
Member
59
06-12-2016, 03:04 PM
#16
The file size is now at 300MB.
K
KochJus7in
06-12-2016, 03:04 PM #16

The file size is now at 300MB.

Z
ziad347
Junior Member
5
06-17-2016, 12:26 PM
#17
The problem mainly comes from the complexity of the code used by the forum, and there aren't many solutions available. It's a recognized issue, and we hope it gets resolved in the upcoming forum update next year. For now, the best workaround on Firefox is to go to about:memory and click measure. But once Firefox shifts to a multi-process model (which is still in development), measuring per-tab memory usage will become much simpler.
Z
ziad347
06-17-2016, 12:26 PM #17

The problem mainly comes from the complexity of the code used by the forum, and there aren't many solutions available. It's a recognized issue, and we hope it gets resolved in the upcoming forum update next year. For now, the best workaround on Firefox is to go to about:memory and click measure. But once Firefox shifts to a multi-process model (which is still in development), measuring per-tab memory usage will become much simpler.

J
Jayhawk_Down
Senior Member
350
06-17-2016, 08:36 PM
#18
Here, the Firefox extension NoScript shines, allowing you to disable unnecessary scripts and let only the essential code run. This minimizes the strain on your CPU and memory, conserves energy by cutting down on unnecessary processing, and helps protect the environment by reducing wasteful code execution.
J
Jayhawk_Down
06-17-2016, 08:36 PM #18

Here, the Firefox extension NoScript shines, allowing you to disable unnecessary scripts and let only the essential code run. This minimizes the strain on your CPU and memory, conserves energy by cutting down on unnecessary processing, and helps protect the environment by reducing wasteful code execution.

Pages (2): Previous 1 2