PM v27b3 memory issues

This board is for discussions, bug reports, etc. for pre-releases of the v27 milestone codenamed "Tycho".

Since the beta phase is over, this board is closed for new posts/topics.

Moderator: satrow

freefrog

PM v27b3 memory issues

Unread post by freefrog » 2016-11-04, 17:27

For some reason the PM v27b3 (x64 portable) is taking GB's of memory while sitting idle usually in combination with 1 core on full use while increasing the used memory. I have observed it go to >5GB on an 8GB Win10 and at one point or another it starts going down to about 0,6-1,5GB while moving the free-ed up memory to the System and compressed memory process. The system is not crashing but the page file has grown to the allowed limit of 16GB and the OS other processes are negatively impacted during the memory increase/decrease time.

P.S. Probably not related to addons since the only one loaded is NewsFox)

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 23689
Joined: 2011-08-28, 17:27
Location: 58°2'16"N 14°58'31"E
Contact:

Re: PM v27b3 memory issues

Unread post by Moonchild » 2016-11-04, 17:47

Checking about:memory when memory usage is out of bounds will help us more than a generic description "it's eating memory".
I never heard of the extension before, but if it's not a native Pale Moon extension then any single extension can cause potential issues.
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne
"I'm afraid you have me mistaken for someone who can be shamed by a child." -- Quillspawn

freefrog

Re: PM v27b3 memory issues

Unread post by freefrog » 2016-11-04, 17:54

It's an RSS reader I've been using for years and haven't had problems with it until now. I can't measure the memory usage while it is going up or down because the UI hangs. This is right after the increase:
1,496.74 MB (100.0%) -- explicit
├────660.62 MB (44.14%) ── heap-unclassified
├────456.49 MB (30.50%) -- add-ons

In this case it went up to ~2,5GB and then down to 1,5.

While writing this it jumped again:

2,003.69 MB (100.0%) -- explicit
├──1,169.24 MB (58.35%) ── heap-unclassified
├────456.40 MB (22.78%) -- add-ons
Explicit Allocations

2,003.69 MB (100.0%) -- explicit
├──1,169.24 MB (58.35%) ── heap-unclassified
├────456.40 MB (22.78%) ++ add-ons
├────175.90 MB (08.78%) ++ window-objects
├─────78.87 MB (03.94%) ++ js-non-window
├─────50.19 MB (02.50%) ++ heap-overhead
├─────45.86 MB (02.29%) ++ (20 tiny)
└─────27.22 MB (01.36%) ++ storage/sqlite

Other Measurements

134,217,727.94 MB (100.0%) -- address-space
├──134,214,751.18 MB (100.0%) ── free [386]
└────────2,976.76 MB (00.00%) ++ (2 tiny)

55.53 MB (100.0%) ++ decommitted

5,083 (100.0%) ++ event-counts

4.12 MB (100.0%) ++ images

378.20 MB (100.0%) ++ js-main-runtime

338 (100.0%) ++ js-main-runtime-compartments

125.56 MB (100.0%) ++ js-main-runtime-gc-heap-committed

116 (100.0%) ++ message-manager

1,176 (100.0%) ++ observer-service

290 (100.0%) ++ observer-service-suspect

701 (100.0%) ++ preference-service

333.02 MB (100.0%) ++ window-objects

0.00 MB ── canvas-2d-pixels
61.79 MB ── d3d11-shared-textures
0.00 MB ── d3d9-shared-texture
0.00 MB ── d3d9-shared-textures
0.00 MB ── d3d9-surface-image
0.00 MB ── gfx-d2d-surface-cache
4.00 MB ── gfx-d2d-surface-vram
0.00 MB ── gfx-d2d-vram-draw-target
0.00 MB ── gfx-d2d-vram-source-surface
0.03 MB ── gfx-surface-win32
0.00 MB ── gfx-textures
0.00 MB ── gfx-tiles-waste
0 ── ghost-windows
118.75 MB ── gpu-committed
0.00 MB ── gpu-dedicated
143.37 MB ── gpu-shared
1,823.68 MB ── heap-allocated
2,024 ── heap-chunks
1.00 MB ── heap-chunksize
1,834.72 MB ── heap-committed
2,024.00 MB ── heap-mapped
0.60% ── heap-overhead-ratio
0.53 MB ── imagelib-surface-cache-estimated-locked
1.14 MB ── imagelib-surface-cache-estimated-total
1.37 MB ── js-main-runtime-temporary-peak
2,209.85 MB ── private
2,083.35 MB ── resident
2,976.70 MB ── vsize
131,778,644.56 MB ── vsize-max-contiguous
And once more:

2,111.33 MB (100.0%) -- explicit
├────780.24 MB (36.95%) ++ window-objects
├────669.24 MB (31.70%) ── heap-unclassified
├────458.66 MB (21.72%) ++ add-ons
Explicit Allocations

2,111.33 MB (100.0%) -- explicit
├────780.24 MB (36.95%) ++ window-objects
├────669.24 MB (31.70%) ── heap-unclassified
├────458.66 MB (21.72%) ++ add-ons
├─────93.40 MB (04.42%) ++ js-non-window
├─────51.80 MB (02.45%) ++ (20 tiny)
├─────30.66 MB (01.45%) ++ heap-overhead
└─────27.33 MB (01.29%) ++ storage/sqlite

Other Measurements

134,217,727.94 MB (100.0%) -- address-space
├──134,214,622.21 MB (100.0%) ── free [443]
└────────3,105.72 MB (00.00%) ++ (2 tiny)

17.68 MB (100.0%) ++ decommitted

5,577 (100.0%) ++ event-counts

4.86 MB (100.0%) ++ images

940.42 MB (100.0%) ++ js-main-runtime

355 (100.0%) ++ js-main-runtime-compartments

166.41 MB (100.0%) ++ js-main-runtime-gc-heap-committed

131 (100.0%) ++ message-manager

1,277 (100.0%) ++ observer-service

320 (100.0%) ++ observer-service-suspect

712 (100.0%) ++ preference-service

391.92 MB (100.0%) ++ window-objects

0.00 MB ── canvas-2d-pixels
76.92 MB ── d3d11-shared-textures
0.00 MB ── d3d9-shared-texture
0.00 MB ── d3d9-shared-textures
0.00 MB ── d3d9-surface-image
0.00 MB ── gfx-d2d-surface-cache
4.00 MB ── gfx-d2d-surface-vram
0.00 MB ── gfx-d2d-vram-draw-target
0.00 MB ── gfx-d2d-vram-source-surface
0.19 MB ── gfx-surface-win32
0.00 MB ── gfx-textures
0.00 MB ── gfx-tiles-waste
0 ── ghost-windows
139.95 MB ── gpu-committed
0.00 MB ── gpu-dedicated
211.88 MB ── gpu-shared
1,909.40 MB ── heap-allocated
2,124 ── heap-chunks
1.00 MB ── heap-chunksize
1,921.53 MB ── heap-committed
2,124.00 MB ── heap-mapped
0.63% ── heap-overhead-ratio
0.78 MB ── imagelib-surface-cache-estimated-locked
0.80 MB ── imagelib-surface-cache-estimated-total
1.37 MB ── js-main-runtime-temporary-peak
2,298.89 MB ── private
2,154.51 MB ── resident
3,105.66 MB ── vsize
131,778,264.56 MB ── vsize-max-contiguous
P.S. NewsFox was usually taking about 250-400MB on v26.5.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 23689
Joined: 2011-08-28, 17:27
Location: 58°2'16"N 14°58'31"E
Contact:

Re: PM v27b3 memory issues

Unread post by Moonchild » 2016-11-04, 18:14

An add-on taking that much memory is suspect to begin with. heap-unclassified usually means memory that was not properly deallocated.
See if the issue occurs with the add-on not installed (not just disabled, but completely removed)
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne
"I'm afraid you have me mistaken for someone who can be shamed by a child." -- Quillspawn

freefrog

Re: PM v27b3 memory issues

Unread post by freefrog » 2016-11-08, 07:16

You are correct that it's the NewsFox addon, I'll submit a bug report to the author but could you check PM as well (just in case) since the problem is not present in v26.5.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 23689
Joined: 2011-08-28, 17:27
Location: 58°2'16"N 14°58'31"E
Contact:

Re: PM v27b3 memory issues

Unread post by Moonchild » 2016-11-08, 13:56

You have to understand that we have made massive changes to the back-end of the browser. There isn't anything specific "to check"; rather, it's likely that the add-on in question needs to be updated t work with changed APIs and/or calls.
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"If you want to build a better world for yourself, you have to be willing to build one for everybody." -- Coyote Osborne
"I'm afraid you have me mistaken for someone who can be shamed by a child." -- Quillspawn

freefrog

Re: PM v27b3 memory issues

Unread post by freefrog » 2016-11-14, 07:43

Turns out the problem wasn't the addon but one of the feeds (it was redirecting to a 100MB file), once I removed it everything returned to normal.

P.S. Feel free to close the threat.

Locked