Re: Slowdowns over time when using SeaMonkey
Jonathan Wilson wrote: > > Is this kind of hanging/freezing/slowdown a known thing? Is there a > bugzilla bug (or bugs) that cover this issue? Is there anything that can > be done to mitigate or work around the issue? Could one of my plugins (I > use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger > and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, > Silverlight, Window Live Photos and Flash as plugins) be the cause of > the problems? I get this too on 2.49.2, Win8.1 64bit and it is frustrating me to no end. To be honest, it has gotten progressively bad since 2.46. :( It's either an optimization issue or something in how we use the backend isn't working well. I have zero idea/clue as to what's bugging this. Frank, got any ideas? Or do we need to tweak our mozconfigs to build SeaMonkey 'better'? (The mozconfig setup in m-c's browser/ requires some time to unravel the spaghettiness. Kinda reminds me of BASIC programming..) ;P Edmund ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
On 3/20/2018 7:51 AM, TCW wrote: On 3/20/2018 9:38 AM, Ed Mullen wrote: On 3/20/2018 at 10:22 AM, TCW created this epitome of digital genius: On 3/20/2018 9:10 AM, Ed Mullen wrote: On 3/20/2018 at 9:55 AM, TCW created this epitome of digital genius: On 3/20/2018 8:36 AM, Jonathan Wilson wrote: If I use SeaMonkey (2.49.2 which seems to be the latest version) for a while and visit different sites and open and close windows and such, eventually it gets to the point where it slows down to the point of almost hanging and I need to close a bunch of windows (which takes ages since SeaMonkey is running so slow) before SeaMonkey will start being usable again. In some cases I have to force-close SeaMonkey completly because its totally hung and simply wont respond to my inputs. I have noticed that using Google Maps and panning around is a great way to make this hanging/freezing/etc happen faster. The last time it totally hung Task Manager told me there was almost no free physical memory (I have a total of 8GB) and that SeaMonkey was using a very large amount of RAM. I also noticed that when I attached to SM with a debugger, it was hanging somewhere in the windows memory allocation code (i.e. that was what was on top of the call stack) with some mozglue memory allocation code the next thing after the windows code. Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? Yes, I have seen this as well. I am using a build of SM 2.53 and I've seen it happen browsing regular sites. It seems to be either a memory leak or the browser not releasing memory though garbage collection / cycle collection. I would not hold out hope for a fix since there are not many people working on SM at the moment. I'm not seeing this at all. SM 2.49.2 Win 10 Pro 64-bit. I suspect an add-on or combination of add-ons. I suggest trying Safe Mode to see if that is it. I thought it was an add-on as well. Frank-Reiner had me switch to uBlock as I too thought ABP was culprit. Nope. I can 100% repro it when browsing on Momondo and AirBNB for a short period of time (15-30 minutes) on my home or office PC. I'm on Win 7 x64 but I doubt it makes any difference. Have you tried Safe Mode? Yup. I noticed uBlock Origin's counter goes up due to blocking connections. That cause major slow downs. :( -- "I really believe I've been a good person. Not perfect - forget about perfect - but just learning by what I was taught and living by my own values. I might have stepped on a few ants - and a few other things as well - but I've never hurt anybody." --Kiri Te Kanawa Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly. /\___/\ Ant(Dude) @ Personal Web Site http://antfarm.ma.cx / /\ /\ \ | |o o| | If crediting, then use Ant nickname and URL/link. \ _ / Axe ANT from its address if e-mailing privately. ( ) ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
On 3/20/2018 2:44 PM, EE wrote: Bill Spikowski wrote: S Slicer wrote: Jonathan Wilson wrote: Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? I see this too. Very noticeable on Facebook. Same here - a problem for many years now; don't expect a fix. I finally put a "Kill Seamonkey" icon on my desktop and use it frequently when things slow down. I have not noticed that problem with SeaMonkey on MacOS. I clear the cache and history after every browsing session, which probably helps. So do I. It's not cache but likely bad web site design. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
Bill Spikowski wrote: S Slicer wrote: Jonathan Wilson wrote: Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? I see this too. Very noticeable on Facebook. Same here - a problem for many years now; don't expect a fix. I finally put a "Kill Seamonkey" icon on my desktop and use it frequently when things slow down. I have not noticed that problem with SeaMonkey on MacOS. I clear the cache and history after every browsing session, which probably helps. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
Bill Spikowski wrote: S Slicer wrote: Jonathan Wilson wrote: Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? I see this too. Very noticeable on Facebook. Same here - a problem for many years now; don't expect a fix. I finally put a "Kill Seamonkey" icon on my desktop and use it frequently when things slow down. I might add that this icon is right next to my "Kill Chrome," "Kill Opera" and "Kill Firefox" buttons -- all of them get bogged down from time to time. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
S Slicer wrote: Jonathan Wilson wrote: Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? I see this too. Very noticeable on Facebook. Same here - a problem for many years now; don't expect a fix. I finally put a "Kill Seamonkey" icon on my desktop and use it frequently when things slow down. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
Jonathan Wilson wrote: If I use SeaMonkey (2.49.2 which seems to be the latest version) for a while and visit different sites and open and close windows and such, eventually it gets to the point where it slows down to the point of almost hanging and I need to close a bunch of windows (which takes ages since SeaMonkey is running so slow) before SeaMonkey will start being usable again. In some cases I have to force-close SeaMonkey completly because its totally hung and simply wont respond to my inputs. I have noticed that using Google Maps and panning around is a great way to make this hanging/freezing/etc happen faster. The last time it totally hung Task Manager told me there was almost no free physical memory (I have a total of 8GB) and that SeaMonkey was using a very large amount of RAM. I also noticed that when I attached to SM with a debugger, it was hanging somewhere in the windows memory allocation code (i.e. that was what was on top of the call stack) with some mozglue memory allocation code the next thing after the windows code. Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? I see this too. Very noticeable on Facebook. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
On 3/20/2018 9:38 AM, Ed Mullen wrote: On 3/20/2018 at 10:22 AM, TCW created this epitome of digital genius: On 3/20/2018 9:10 AM, Ed Mullen wrote: On 3/20/2018 at 9:55 AM, TCW created this epitome of digital genius: On 3/20/2018 8:36 AM, Jonathan Wilson wrote: If I use SeaMonkey (2.49.2 which seems to be the latest version) for a while and visit different sites and open and close windows and such, eventually it gets to the point where it slows down to the point of almost hanging and I need to close a bunch of windows (which takes ages since SeaMonkey is running so slow) before SeaMonkey will start being usable again. In some cases I have to force-close SeaMonkey completly because its totally hung and simply wont respond to my inputs. I have noticed that using Google Maps and panning around is a great way to make this hanging/freezing/etc happen faster. The last time it totally hung Task Manager told me there was almost no free physical memory (I have a total of 8GB) and that SeaMonkey was using a very large amount of RAM. I also noticed that when I attached to SM with a debugger, it was hanging somewhere in the windows memory allocation code (i.e. that was what was on top of the call stack) with some mozglue memory allocation code the next thing after the windows code. Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? Yes, I have seen this as well. I am using a build of SM 2.53 and I've seen it happen browsing regular sites. It seems to be either a memory leak or the browser not releasing memory though garbage collection / cycle collection. I would not hold out hope for a fix since there are not many people working on SM at the moment. I'm not seeing this at all. SM 2.49.2 Win 10 Pro 64-bit. I suspect an add-on or combination of add-ons. I suggest trying Safe Mode to see if that is it. I thought it was an add-on as well. Frank-Reiner had me switch to uBlock as I too thought ABP was culprit. Nope. I can 100% repro it when browsing on Momondo and AirBNB for a short period of time (15-30 minutes) on my home or office PC. I'm on Win 7 x64 but I doubt it makes any difference. Have you tried Safe Mode? Yup. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
On 3/20/2018 at 10:22 AM, TCW created this epitome of digital genius: On 3/20/2018 9:10 AM, Ed Mullen wrote: On 3/20/2018 at 9:55 AM, TCW created this epitome of digital genius: On 3/20/2018 8:36 AM, Jonathan Wilson wrote: If I use SeaMonkey (2.49.2 which seems to be the latest version) for a while and visit different sites and open and close windows and such, eventually it gets to the point where it slows down to the point of almost hanging and I need to close a bunch of windows (which takes ages since SeaMonkey is running so slow) before SeaMonkey will start being usable again. In some cases I have to force-close SeaMonkey completly because its totally hung and simply wont respond to my inputs. I have noticed that using Google Maps and panning around is a great way to make this hanging/freezing/etc happen faster. The last time it totally hung Task Manager told me there was almost no free physical memory (I have a total of 8GB) and that SeaMonkey was using a very large amount of RAM. I also noticed that when I attached to SM with a debugger, it was hanging somewhere in the windows memory allocation code (i.e. that was what was on top of the call stack) with some mozglue memory allocation code the next thing after the windows code. Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? Yes, I have seen this as well. I am using a build of SM 2.53 and I've seen it happen browsing regular sites. It seems to be either a memory leak or the browser not releasing memory though garbage collection / cycle collection. I would not hold out hope for a fix since there are not many people working on SM at the moment. I'm not seeing this at all. SM 2.49.2 Win 10 Pro 64-bit. I suspect an add-on or combination of add-ons. I suggest trying Safe Mode to see if that is it. I thought it was an add-on as well. Frank-Reiner had me switch to uBlock as I too thought ABP was culprit. Nope. I can 100% repro it when browsing on Momondo and AirBNB for a short period of time (15-30 minutes) on my home or office PC. I'm on Win 7 x64 but I doubt it makes any difference. Have you tried Safe Mode? -- Ed Mullen http://edmullen.net/ A good scapegoat is almost as good as a solution. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
On 3/20/2018 9:10 AM, Ed Mullen wrote: On 3/20/2018 at 9:55 AM, TCW created this epitome of digital genius: On 3/20/2018 8:36 AM, Jonathan Wilson wrote: If I use SeaMonkey (2.49.2 which seems to be the latest version) for a while and visit different sites and open and close windows and such, eventually it gets to the point where it slows down to the point of almost hanging and I need to close a bunch of windows (which takes ages since SeaMonkey is running so slow) before SeaMonkey will start being usable again. In some cases I have to force-close SeaMonkey completly because its totally hung and simply wont respond to my inputs. I have noticed that using Google Maps and panning around is a great way to make this hanging/freezing/etc happen faster. The last time it totally hung Task Manager told me there was almost no free physical memory (I have a total of 8GB) and that SeaMonkey was using a very large amount of RAM. I also noticed that when I attached to SM with a debugger, it was hanging somewhere in the windows memory allocation code (i.e. that was what was on top of the call stack) with some mozglue memory allocation code the next thing after the windows code. Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? Yes, I have seen this as well. I am using a build of SM 2.53 and I've seen it happen browsing regular sites. It seems to be either a memory leak or the browser not releasing memory though garbage collection / cycle collection. I would not hold out hope for a fix since there are not many people working on SM at the moment. I'm not seeing this at all. SM 2.49.2 Win 10 Pro 64-bit. I suspect an add-on or combination of add-ons. I suggest trying Safe Mode to see if that is it. I thought it was an add-on as well. Frank-Reiner had me switch to uBlock as I too thought ABP was culprit. Nope. I can 100% repro it when browsing on Momondo and AirBNB for a short period of time (15-30 minutes) on my home or office PC. I'm on Win 7 x64 but I doubt it makes any difference. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
On 3/20/2018 at 9:55 AM, TCW created this epitome of digital genius: On 3/20/2018 8:36 AM, Jonathan Wilson wrote: If I use SeaMonkey (2.49.2 which seems to be the latest version) for a while and visit different sites and open and close windows and such, eventually it gets to the point where it slows down to the point of almost hanging and I need to close a bunch of windows (which takes ages since SeaMonkey is running so slow) before SeaMonkey will start being usable again. In some cases I have to force-close SeaMonkey completly because its totally hung and simply wont respond to my inputs. I have noticed that using Google Maps and panning around is a great way to make this hanging/freezing/etc happen faster. The last time it totally hung Task Manager told me there was almost no free physical memory (I have a total of 8GB) and that SeaMonkey was using a very large amount of RAM. I also noticed that when I attached to SM with a debugger, it was hanging somewhere in the windows memory allocation code (i.e. that was what was on top of the call stack) with some mozglue memory allocation code the next thing after the windows code. Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? Yes, I have seen this as well. I am using a build of SM 2.53 and I've seen it happen browsing regular sites. It seems to be either a memory leak or the browser not releasing memory though garbage collection / cycle collection. I would not hold out hope for a fix since there are not many people working on SM at the moment. I'm not seeing this at all. SM 2.49.2 Win 10 Pro 64-bit. I suspect an add-on or combination of add-ons. I suggest trying Safe Mode to see if that is it. -- Ed Mullen http://edmullen.net/ Five out of four people have trouble with fractions. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Slowdowns over time when using SeaMonkey
On 3/20/2018 8:36 AM, Jonathan Wilson wrote: If I use SeaMonkey (2.49.2 which seems to be the latest version) for a while and visit different sites and open and close windows and such, eventually it gets to the point where it slows down to the point of almost hanging and I need to close a bunch of windows (which takes ages since SeaMonkey is running so slow) before SeaMonkey will start being usable again. In some cases I have to force-close SeaMonkey completly because its totally hung and simply wont respond to my inputs. I have noticed that using Google Maps and panning around is a great way to make this hanging/freezing/etc happen faster. The last time it totally hung Task Manager told me there was almost no free physical memory (I have a total of 8GB) and that SeaMonkey was using a very large amount of RAM. I also noticed that when I attached to SM with a debugger, it was hanging somewhere in the windows memory allocation code (i.e. that was what was on top of the call stack) with some mozglue memory allocation code the next thing after the windows code. Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? Yes, I have seen this as well. I am using a build of SM 2.53 and I've seen it happen browsing regular sites. It seems to be either a memory leak or the browser not releasing memory though garbage collection / cycle collection. I would not hold out hope for a fix since there are not many people working on SM at the moment. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Slowdowns over time when using SeaMonkey
If I use SeaMonkey (2.49.2 which seems to be the latest version) for a while and visit different sites and open and close windows and such, eventually it gets to the point where it slows down to the point of almost hanging and I need to close a bunch of windows (which takes ages since SeaMonkey is running so slow) before SeaMonkey will start being usable again. In some cases I have to force-close SeaMonkey completly because its totally hung and simply wont respond to my inputs. I have noticed that using Google Maps and panning around is a great way to make this hanging/freezing/etc happen faster. The last time it totally hung Task Manager told me there was almost no free physical memory (I have a total of 8GB) and that SeaMonkey was using a very large amount of RAM. I also noticed that when I attached to SM with a debugger, it was hanging somewhere in the windows memory allocation code (i.e. that was what was on top of the call stack) with some mozglue memory allocation code the next thing after the windows code. Is this kind of hanging/freezing/slowdown a known thing? Is there a bugzilla bug (or bugs) that cover this issue? Is there anything that can be done to mitigate or work around the issue? Could one of my plugins (I use Addblock, ChatZilla, DOM Inspector, Geolocater, JavaScript Debugger and User Agent Switcher as extentions plus Acrobat, NVIDIA 3D, Silverlight, Window Live Photos and Flash as plugins) be the cause of the problems? ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
