Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090714 SeaMonkey/2.1a1pre - Build ID: 20090714000750 Two hangs out of two runs so far, each time after only a few minutes. One of them locked my keyboard (even Ctrl-Alt-F2 stopped working). Not sure how people "other than me" can reproduce it, hence the UNCONFIRMED status. Morality: Interesting product but not yet dogfoodable (for me at least, "I'm not a Mozilla developer"). I'm going back to 2.0b1pre but I'll keep an eye on 2.1 too.

P.S. I think I recall what I did that locked the keyboard for all applications: hitting n (Next unread) in SeaMonkey MailNews.

Also happened on my Mac using Seamonkey 2.0 stable release, the information I was able to get back from finder exceeded the max limit on bugzilla so I had to pastebin the output -> http://pastebin.com/f7ad7aa6

(In reply to comment #2) > Also happened on my Mac using Seamonkey 2.0 stable release, the information I > was able to get back from finder exceeded the max limit on bugzilla so I had to > pastebin the output -> http://pastebin.com/f7ad7aa6 In 2.0 I've had hangs but not forever (waiting no more than a minute or two let me continue) and not blocking other apps (e.g. I could run Patience, Minesweeper, YaST, ftp, whatever, while waiting for SeaMonkey to react).

Tony, do you still have this problem? If not please close this bug as WORKSFORME.

(In reply to comment #4) > Tony, do you still have this problem? If not please close this bug as > WORKSFORME. In 2.1x I don't know: Looks like I reneged on my word in comment #0 and let Sm 2.1 go unwatched. In 2.0.4pre I still experience the hangs described in comment #3; I believe they're worse (longer and heavier IYSWIM) when ChatZilla is running, connected and joined, because of the additional I/O and CPU workload. I recently stopped using ChatZilla (in favour of Konversation, which has a less user-friendly interface but has the advantage of being self-contained) and the hangs have gone back to something not really fun, but tolerable once one gets used to them. :-/

Please try in Safe mode ( http://kb.mozillazine.org/Talk:Safe_Mode#Safe_Mode_in_SeaMonkey_2 ). Conflict keyboard shortcut with Linux keyboard shortcut?

Is package from ftp server mozilla or repository Linux distribution?

(In reply to comment #7) > Is package from ftp server mozilla or repository Linux distribution? The SeaMonkey versions I use are nightlies from ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-comm-1.9.1/ or, less often, builds from the latest "numbered" subdirectory of ftp://ftp.mozilla.org/pub/mozilla.org/seamonkey/tinderbox-builds/comm-1.9.1-linux/ I install them with rm -Rvf /usr/local/seamonkey tar -jxvC /usr/local -f seamo*.tar.bz2 after checking that (1) no "seamonkey" or "seamonkey-bin" processes are running; (2) only the latest SeaMonkey .tar.bz2 (and no older version) exists in the current directory. A softlink /usr/local/bin/seamonkey -> ../seamonkey/seamonkey makes this the first "seamonkey" in the $PATH regardless of whether or not the openSUSE distro installs another one, e.g. in /usr/bin My current build is the following: - User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9pre) Gecko/20100311 SeaMonkey/2.0.4pre - Build ID: 20100311004501 (In reply to comment #6) > Please try in Safe mode [...] I will, when I get my next nightlies of SeaMonkey and Sunbird, in maybe six hours or a little more. > Conflict keyboard shortcut with Linux keyboard shortcut? I don't think so; these "temporary hangs" seem to be uncorrelated to keyboard use; AFAICT they also happen when I'm typing plaintext in the Mailer, or using the mouse.

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9pre) Gecko/20100312 SeaMonkey/2.0.4pre Yes, it also happens in safe mode (and now, after using "safe mode" for some minutes, or maybe tens of them, I'll restart in "unsafe" mode because my add-ons are there for a reason).

...sorry if the previous comment seemed flippant, I didn't mean to.

Mozilla/5.0 (X11; Linux i686; rv:2.0b8pre) Gecko/20101212 Firefox/4.0b8pre SeaMonkey/2.1b2pre - Build ID: 20101212003013 Here's the present status of the matter from my POV: - SeaMonkey is dogfoodable (if I'm entitled to use that expression) but Lightning isn't. Lately Lightning doesn't display anything (bug 615996), before that it used to crash at startup (bug 611711). - Frequent temporary pseudo-hangs using high CPU, lasting from tens of seconds to minutes, with spontaneous recovery. If Chatzilla is connected to moznet any such pseudo-hang may cause a "ping timeout" disconnect. Freenode seems more lenient. Not really sure what is the cause of these pseudo-hangs, I suspect getting & filtering mail. (4 POP accounts including one with very high traffic including bugmail; one low-traffic Movemail account [8 messages per week, usually very short]; all "usual" (for me) kinds of incoming mail get filtered out of Inbox to specific "Local Folders" folders; many RSS/Atom feeds; several news.m.o. newsgroups) - Somewhat less frequent, but more severe, real hangs with WCHAN seen as futex_wait_queue_me in ps: I've reported this separately as bug 570316. Usually zero CPU (i.e. no more total CPU activity than if Sm weren't running), very rarely high CPU. No response to keyboard or mouse, no painting of chrome or content at focusgain, ChatZilla (if running) gets ping-timed-out of all networks; Sm still responds to signals (kill -15 will kill, kill -4 or kill -11 will not only kill but also bring up Breakpad).

(In reply to comment #5) > (In reply to comment #4) > > Tony, do you still have this problem? If not please close this bug as > > WORKSFORME. > > In 2.1x I don't know: Looks like I reneged on my word in comment #0 and let Sm > 2.1 go unwatched. > > In 2.0.4pre I still experience the hangs described in comment #3; I believe > they're worse (longer and heavier IYSWIM) when ChatZilla is running, connected > and joined, because of the additional I/O and CPU workload. I recently stopped > using ChatZilla (in favour of Konversation, which has a less user-friendly > interface but has the advantage of being self-contained) and the hangs have > gone back to something not really fun, but tolerable once one gets used to > them. :-/ perhaps using -no-remote to start more than instance of SM, and segregate mailnews usage from browser, would enable better diagnosis of the 3 or more issues you have cited? and if you are using lightning, have a look at bug 441710 compose and UI occasionally freezes/slow for 3-60 seconds unexpectedly and continually with calendar/lightning

Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120320 Firefox/14.0a1 SeaMonkey/2.11a1 ID:20120320003047 I'm not seeing this on trunk anymore. Maybe the fact that I'm on a faster processor (and twin-core 64-bit) is a reason. Another possibility is that I've dropped Lightning in favour of the last Sunbird 1.0b2pre (dated 2010-05-26; yes I know it's unsupported).