806075 - Seamonkey OS X will not quit with 20-30 tabs in 3 windows

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Steve Manser]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.26.14 (KHTML, like Gecko) Version/6.0.1 Safari/536.26.14

Steps to reproduce:

Just using Seamonkey 2.13.1 as usual, I have 3 lots of windows, financial (yahoo, nasdaq etc), news (mainly MacNN) and general (bbc weather, digital photo review, etc) with about 20-30 tabs across the 3 windows.

In the past I have had slow closing from about 2.11.x but now with 2.12.x and 2.13.x I have had to quit after a while with slow performance (running iMac 27" 2.8Ghz i7, 4Gb RAM and OS X 10.7.5) no other apps seem to have issue or other browsers.

Ram in use hits about 2.8Gb and then sits there, with 1.2Gb free and the machine just really slows down and things like iTunes start skipping playing music (only other app open) so the machine seems to be under heavy load or is being held from performing real time actions by Seamonkey.

Anyway, that's what I am seeing, if you need any other info please ask.

Rgds,
Steve


Actual results:

On quit Seamonkey takes 1-2 mins to close all windows, then all that's left is the Dock icon, showng number of unread messages and the machine seems to be doing nothing, after 10 mins I just have to force quit app.


Expected results:

Should quit, then within a minute or to should complete quit process but never does.

Comment 1

[Philip Chee]

Can you try re-starting SeaMonkey in safe-mode?
Go Help->Restart with Add-ons Disabled.

Comment 2

[Steve Manser]

No problem, as this issue can be triggered only by lots of tabs, will try this next time I have a lot tabs open, cut these down to stop the issue.

Thanks for the quick response tho, is there any way to see a sort of activity view in Seamonkey, so maybe I can see what it is hanging up on and report back or some log mode so I can send this to you next time it happens?

Rgds,
Steve

Comment 3

[Tony Mechelynck [:tonymec]]

(In reply to Steve Manser from comment #2)
> No problem, as this issue can be triggered only by lots of tabs, will try
> this next time I have a lot tabs open, cut these down to stop the issue.
> 
> Thanks for the quick response tho, is there any way to see a sort of
> activity view in Seamonkey, so maybe I can see what it is hanging up on and
> report back or some log mode so I can send this to you next time it happens?
> 
> Rgds,
> Steve

To see what the program is hanging on is not an obvious thing. If it happens again, you may try to force-crash the program (the Nightly Tester Tools extension has, on some platforms, a menuitem to do this) and send a stack trace: on restarting from the crash, you should find a new bp-something item in about:crashes, where the "something" part is a long string of hex digits with some dashes. Pasting that bp-something string (with the initial bp-) in a bug comment might perhaps help the developers find out where the program was hanging.

Comment 4

[therube]

> Ram in use hits about 2.8Gb

That is a lot IMO.
(Said by someone who uses LOTS of windows/tabs [65/833] & is sitting at 1.3 GB at the moment).

Is the OS 32 or 64-bit?  And SeaMonkey is 32-bit?
Is is normal for SeaMonkey to use, or to be able to use, that much RAM on Mac/Linux without issue?

> this issue can be triggered only by lots of tabs

Will opening the same sites in a new, clean Profile also cause the hang on Quit?
(You could copy the sessionstore.json file from your existing Profile into the new in order to load the same set of sites.)

Any difference if you disable Plugins (Tools | Addons Manager) other then Flash or whatever it is you need for the particular sites)?  What other plugins do you have?
 
 
Here are a couple of bugs, both "FIXED", but maybe something there will stand out?

Bug 636210 - Hang when quitting SeaMonkey if "Always clear my private data when I close SeaMonkey" is combined with "Ask me before clearing private data"

Bug 789773 - nsIWebProgressListener implementations referencing the load's window in onStateChange() (like NoScript or Roboform) cause popup loads to be aborted and the browser to hang on exit