Possible Memory Leak about synoloader HOT 5 CLOSED

20140616
Restart FF but Not Mint
CPU 0% Mem 141MB

Disable all extensions except Synoloader

20140618
Had to go onsite with my laptop so it got restarted
Up to then No problem with only Synoloader extension loaded into FFox
Re-started Laptop at around 17:00 yesterday

at 09:00 today FF was Frozen CPU 100%, Memory 2.1GB
Running overnight with 8 tabs open
Synology DS212 Web Interface with Download Manager auto updating, local
My Router Monitor auto updating, local
Juniper Router Web Management page remote
Zyxel Router Management Page Remote
Zyxel Site Page - Static
Another Zyxel Site Page - static
A blog web page static

I opened the Addons Page to check that Synoloader was the Only extension loaded

As a control, I checked on my other Acer laptop
This has been running, pretty much idle for 1.5 days CPU & Memory for FFox Normal
I opened the DSM Web Management page and opened Download Manager

Returning to my Main Laptop, FFX had freed up, CPU 0-20% 547MB Memory
So in this instance the issue cleared itself.

I am beginning to wonder if this has to do with leaving the Synology DSM interface open for extended periods, with Download Manager Constantly updating (Which I often do to monitor downloads overnight)

from synoloader.

As I watch FFox right now the CPU & Memory are creeping up
I have been using two windows earlier, now only one with my two local Device monitoring pages (Router & DS212) Two Remote Router Management Pages - idling, and this page.
Cpu is fluctuating between 10&90% - Memory is now 917MB fluctuating by about 10% but creeping up steadily, it just topped out at 1017MB.
I have taken a memory report from the FFox Troubleshooter and the bulk of it seems to be the "Unclassified Heap"
I have the full file but cannot see how to attach a file to the issue

901.83 MB (100.0%) -- explicit
├──420.04 MB (46.58%) ── heap-unclassified
├──320.57 MB (35.55%) -- window-objects
│ ├──229.68 MB (25.47%) -- top(http://ds212:5000/webman/index.cgi, id=67)
│ │ ├──214.10 MB (23.74%) -- active
│ │ │ ├──213.85 MB (23.71%) -- window(http://ds212:5000/webman/index.cgi)
│ │ │ │ ├──182.21 MB (20.20%) -- dom
│ │ │ │ │ ├──179.69 MB (19.93%) ── orphan-nodes
│ │ │ │ │ └────2.52 MB (00.28%) ++ (5 tiny)
│ │ │ │ ├───19.59 MB (02.17%) -- js-compartment(http://ds212:5000/webman/index.cgi)
│ │ │ │ │ ├──10.51 MB (01.16%) ++ objects
│ │ │ │ │ └───9.08 MB (01.01%) ++ (6 tiny)
│ │ │ │ └───12.05 MB (01.34%) ++ (3 tiny)
│ │ │ └────0.25 MB (00.03%) ++ window(about:blank)
│ │ └───15.57 MB (01.73%) -- js-zone(0x7fb8cd553800)
│ │ ├───9.29 MB (01.03%) ── unused-gc-things
│ │ └───6.29 MB (00.70%) ++ (7 tiny)
│ ├───45.05 MB (05.00%) -- top(#4, id=7466)
│ │ ├──28.20 MB (03.13%) -- cached
│ │ │ ├───9.73 MB (01.08%) ++ window(https://github.com/Lemutar/Synoloader)
│ │ │ ├───9.43 MB (01.05%) ++ window(https://github.com/Lemutar/Synoloader/issues)
│ │ │ └───9.04 MB (01.00%) ++ window(https://github.com/)
│ │ ├──11.21 MB (01.24%) ++ active/window(#4)
│ │ └───5.64 MB (00.63%) ++ js-zone(0x7fb8173cb000)
│ ├───29.54 MB (03.28%) ++ (9 tiny)
│ └───16.31 MB (01.81%) -- top(https://x.x.x.x/login, id=8)
│ ├──12.48 MB (01.38%) ++ active/window(https://x.x.x.x2/login)
│ └───3.83 MB (00.42%) ++ js-zone(0x7fb8dd907800)
├───64.24 MB (07.12%) -- js-non-window
│ ├──39.32 MB (04.36%) -- zones
│ │ ├──29.96 MB (03.32%) ++ zone(0x7fb8ef079800)
│ │ └───9.35 MB (01.04%) ++ (4 tiny)
│ ├──22.86 MB (02.53%) ++ runtime
│ └───2.06 MB (00.23%) ++ gc-heap
├───51.40 MB (05.70%) -- heap-overhead
│ ├──48.57 MB (05.39%) ── waste
│ └───2.83 MB (00.31%) ++ (2 tiny)
├───30.07 MB (03.33%) ++ (20 tiny)
└───15.51 MB (01.72%) -- storage
├──13.52 MB (01.50%) ++ sqlite
└───1.99 MB (00.22%) ++ prefix-set

from synoloader.

https://app.box.com/s/98eeixpccd4l6q5jp0gx
Here's the Memory Report

from synoloader.

Testing on a second Machine
Acer TravelMate 5730 I Core2Duo 4GB Ram
Linux Mint 16 64 bit Updated not quite so regularly
FFox 29.0 with SYnoloader 1.01

Experience pretty much the same thing, after a couple of days FFox Memory is up to 2.0GB

I am beginning to suspect this may not be directly a problem with Synoloader but more with the DSM Web Interface. I typically leave DSM Running with the Download Manager Monitoring window open, displaying downloads ordered by download speed, which means the display is constantly re-ordering during each refresh every 30 seconds. Obviously this means that FFox is constantly working.
I am going to run a test without Synoloader, and Clean Reset FFox working only with the DSM interface.

from synoloader.

Possible False Alarm
After repeating my testing without Synoloader Extension installed I still get the same symptoms, so it is down to the Synology DSM Webmanager with Download Station, and / or FireFox itself.

On one of my machines I updated Mint16 with latest updates, & rebooted.
Firefox updated to 30.0
Reset Firefox to factory defaults, no extensions or anything.
Open The Synology Management pages, and left them running and I still get the Memory Leak.
I also usually have my router management page open showing the list of hosts and their traffic sorted by download speed, so this also updates every 10 seconds.
So as a last test I will run with ONLY the Router page and see if the symptoms re-occur. If so then I must conclude it is a FireFox issue with constantly updating pages. If not then it is probably a Synology issue.

from synoloader.