Opening wetransfer link blows up memory usage
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.
This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.
Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
Opening wetransfer link blows up memory usage
When I open up a wetransfer link in PM 27.1 memory usage goes up from 0.5 GB to 4GB in a matter of seconds. After this I finished off palemoon in order not no run my system into the ground. An example link: hxxps://www.wetransfer.com/downloads/f3877bc474e4f9cdc3be314050a896fc20170122094821/f4649692e0cd80b39ff5bd06f3426bc020170122094821/ac6620
Re: Opening wetransfer link blows up memory usage
Confirmed, W7.
Link broken deliberately to prevent grief (File has been deleted anyway, no longer available).
Link broken deliberately to prevent grief (File has been deleted anyway, no longer available).
Re: Opening wetransfer link blows up memory usage
So, how are we supposed to move forward with this?
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Opening wetransfer link blows up memory usage
Hi,
Just out of couriosity I gave it a try on Linux mint.
Mem usage (RSS) went up to 4GB, then a message appeared about a script not responding.
I let stop that script, closed the page and everything is fine and smooth...
Just out of couriosity I gave it a try on Linux mint.
Mem usage (RSS) went up to 4GB, then a message appeared about a script not responding.
I let stop that script, closed the page and everything is fine and smooth...
Re: Opening wetransfer link blows up memory usage
Try the link and see what causes this behaviour. It doesn't matter that the link does not provide any files any more. The behaviour is still there and seems quite suspicious to me. I don't see this with Chrome so it could point to a bug in palemoon.
Re: Opening wetransfer link blows up memory usage
I clicked the link out of devilment and the memory shot up to 4gb in a matter of seconds.Dont know what causes it but i have never experienced it before.....had to kill palemoon with my task manager,it wasnt just the browser which locked up either.
user of multiple puppy linuxes..upup,fossapup.scpup,xenialpup.....
Pale moon 29.4.1
Pale moon 29.4.1
Re: Opening wetransfer link blows up memory usage
Problem is still there in PM 27.1.1. Seems that some script is running wild. The tab seems to consumes about 4GB of memory. After stopping the script and closing the tab, the memory is nicely released. It complains about the script at https://cdn.wetransfer.net/ass…a8b9a6ca ... 63bb.js:11 being no longer responsive.
Re: Opening wetransfer link blows up memory usage
Bug is still there in PM 27.1.2. Could anybody have a look at this?
Re: Opening wetransfer link blows up memory usage
The bug is still there in PM 27.2.0. Is any of the devs willing to look into this one?
Re: Opening wetransfer link blows up memory usage
So the problem is that a script is running wild.. Exactly what are you expecting anyone to do about it?
- Gandalfdjh
- Fanatic
- Posts: 126
- Joined: 2014-05-04, 14:00
- Location: United States
- Contact:
Re: Opening wetransfer link blows up memory usage
Do not have much knowledge in this area, but one would assume that script is authored by someone beside PM dev. Thus the issue will have to be fixed by the author/maintainer of the script.rtega wrote:The bug is still there in PM 27.2.0. Is any of the devs willing to look into this one?
Just my two cents on the matter.
1911 remains the service pistol for all ages!
"Speak softly and carry a big stick; you will go far." — Theodore Roosevelt
"Speak softly and carry a big stick; you will go far." — Theodore Roosevelt
Re: Opening wetransfer link blows up memory usage
It'll be a script on the wetransfer site running wild -- something we have no control over if it has a bug (e.g. recursion problem).
Reporting the exact error message about which script has stopped responding would help -- knowing wetransfer though, they will probably not be receptive to bug reports for their scripts if you're not using one of their browsers of choice.
Reporting the exact error message about which script has stopped responding would help -- knowing wetransfer though, they will probably not be receptive to bug reports for their scripts if you're not using one of their browsers of choice.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite