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)
Re: PM v27b3 memory issues
Posted: 2016-11-04, 17:47
by Moonchild
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.
Re: PM v27b3 memory issues
Posted: 2016-11-04, 17:54
by freefrog
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.
P.S. NewsFox was usually taking about 250-400MB on v26.5.
Re: PM v27b3 memory issues
Posted: 2016-11-04, 18:14
by Moonchild
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)
Re: PM v27b3 memory issues
Posted: 2016-11-08, 07:16
by freefrog
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.
Re: PM v27b3 memory issues
Posted: 2016-11-08, 13:56
by Moonchild
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.
Re: PM v27b3 memory issues
Posted: 2016-11-14, 07:43
by freefrog
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.