Steps how to reproduce with SeaMonkey German 2.39 final Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0 from official download area) Gecko/20100101 Firefox/42.0 Build 20151103191810 (Classic Theme) on German WIN7 64bit: Simply work with browser hours and hours having Sidebar history Panel visible. Bug: Again and again the UI becomes unresponsive for few seconds ... 2 minutes (or so). Sometimes additional error message "script unresponsive, close or continue?" related to Script: chrome://communicator/content/history/treeView.js:651 Script: chrome://communicator/content/history/treeView.js:854 Script: chrome://communicator/content/history/treeView.js:181 Script: chrome://communicator/content/history/history-panel.xul:1 Some days it works better, sometimes working with Browser is a real pain. Additional information: a) My wife also observed that that became worse middle to end 2015 when she updated from SM 2.29 (or 2.31?) to 2.35 and later to 2.39. b) This was not a problem at the beginning of 2015
c) I am not 100% sure concerning relation to visible History Siedebar PANEL d) I did not find a clear DUP with <https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=DUPs1239405&sharer_id=41036>, but some Bugs what look a little bit similar
"This was not a problem at the beginning of 2015". Here are the release dates for successive SeaMonkey stable and beta versions near that time (I don't have the dates for Aurora and Trunk): 2014-12-04 2.31 2014-12-16 2.32b1 2014-12-21 2.32b2 2015-01-04 2.32b3 2015-01-13 2.32 2015-02-06 2.32.1 2015-02-26 2.33b1 2015-03-10 2.33 2015-03-24 2.33.1 --------- (2.34 not released) 2015-09-03 2.35 I'll mark it "prudently" in the Whiteboard as 2.31-unaffected but feel free to change that if you have a better recollection of when exactly in 2015 it became a problem. The message you saw can however be a side-effect of increasing system load. I don't use the sidebar, but I've been using more and more tabs recently, and I've been seeing that message now and then at startup, when they all start loading at the same time. (browser.sessionstore.max_concurrent_tabs applies when restoring a session but not when loading a multitab homepage and I've been using one or the other depending on circumstances.)
status-seamonkey2.39: --- → affected
Component: General → Bookmarks & History
Whiteboard: [seamonkey-2.31-unaffected] [seamonkey-2.35-affected]
You need to log in before you can comment on or make changes to this bug.