Linux's SeaMonkey freezes after saving a file.
Ant
SeaMonkey (SM) v1.1.4 from
seamonkey-1.1.14.en-US.linux-i686.installer.tar.gz into
/home/Programs/seamonkey/ ... Mostly everything works, but I noticed
saving files cause SM to freeze hard. CPU usage is in used from SM.
I have to kill its three processes through KDE v3.5.10's terminal since
regular kills weren't enough. At first, I thought it was the old
SessionSaver extension but I was still able to reproduce the freeze. I
I tried to use strace but it seems to stop when SM loads a Web page and
doesn't output anymore.
Any ideas? Thank you in advance. :)
--
"It's kind of an insane case ... 6,000 ants dressed up as rice and
robbed a Chinese restaurant." --Steven Wright
/\___/\
/ /\ /\ \ Phil/Ant @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Nuke ANT from e-mail address: phi...@earthlink.netANT
( ) or ANT...@zimage.com
Ant is currently not listening to any songs on his home computer.
Philip Chee
> Since I had to dump Debian's IceApe a few weeks ago, I had to install
> SeaMonkey (SM) v1.1.4 from
> seamonkey-1.1.14.en-US.linux-i686.installer.tar.gz into
> /home/Programs/seamonkey/ ... Mostly everything works, but I noticed
> saving files cause SM to freeze hard. CPU usage is in used from SM.
>
> I have to kill its three processes through KDE v3.5.10's terminal since
> regular kills weren't enough. At first, I thought it was the old
> SessionSaver extension but I was still able to reproduce the freeze. I
>
> I tried to use strace but it seems to stop when SM loads a Web page and
> doesn't output anymore.
>
> Any ideas? Thank you in advance. :)
Use the -debug command line switch.
seamonkey -debug
Phil
--
Philip Chee <phi...@aleytys.pc.my>, <phili...@gmail.com>
http://flashblock.mozdev.org/ http://xsidebar.mozdev.org
Guard us from the she-wolf and the wolf, and guard us from the thief,
oh Night, and so be good for us to pass.
[ ]BASIC isn't; C stands for Confusing...
* TagZilla 0.066.6
Bill Davidsen
> Since I had to dump Debian's IceApe a few weeks ago, I had to install
> SeaMonkey (SM) v1.1.4 from
> seamonkey-1.1.14.en-US.linux-i686.installer.tar.gz into
> /home/Programs/seamonkey/ ... Mostly everything works, but I noticed
> saving files cause SM to freeze hard. CPU usage is in used from SM.
>
> I have to kill its three processes through KDE v3.5.10's terminal since
> regular kills weren't enough. At first, I thought it was the old
> SessionSaver extension but I was still able to reproduce the freeze. I
>
> I tried to use strace but it seems to stop when SM loads a Web page and
> doesn't output anymore.
>
> Any ideas? Thank you in advance. :)
You might try creating a brand new profile with no extensions or add-ons, and
see if the behavior continues.I will say that I would use 'top' in a window and
see if SM grows over time and behaves badly when it hits 450-550MB in size.
--
Bill Davidsen <davi...@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
clay
> Since I had to dump Debian's IceApe a few weeks ago, I had to install
> SeaMonkey (SM) v1.1.4 from
> seamonkey-1.1.14.en-US.linux-i686.installer.tar.gz into
> /home/Programs/seamonkey/ ... Mostly everything works, but I noticed
> saving files cause SM to freeze hard. CPU usage is in used from SM.
>
> I have to kill its three processes through KDE v3.5.10's terminal since
> regular kills weren't enough. At first, I thought it was the old
> SessionSaver extension but I was still able to reproduce the freeze. I
>
> I tried to use strace but it seems to stop when SM loads a Web page and
> doesn't output anymore.
>
> Any ideas? Thank you in advance. :)
I don't know from SeaMonkey but I installed Firefox in Ubuntu once and
it did exactly the same thing.
Yahoo maps blew up the version from the repos so I installed a 'newer'
release.
Popups like download manager took forever to popup then hung forever
when downloading.
Turned out, I had grabbed a beta from the FTP site.
Installed the release version and everything worked fine.
Phillip Pi
> You might try creating a brand new profile with no extensions or
> add-ons, and see if the behavior continues.I will say that I would use
> 'top' in a window and see if SM grows over time and behaves badly when
> it hits 450-550MB in size.
I did watch top when saving my files. No CPU usage and memory usage
changed. I will try again later.
I will also try a new profile. How do I make a new profile? I don't have
a KDE's menu shortcut for its Profile Manager like in Windows XP Pro.
--
Phillip Pi (aka Ant)
Senior Software Quality Assurance Analyst
Partner Engineering/Internet Service Provider/Symantec Online Services,
Consumer Business Unit
Symantec Corporation
www.symantec.com
-----------------------------------------------------
Email: phill...@symantec.comSYMC (remove SYMC to reply by e-mail)
-----------------------------------------------------
Please do NOT e-mail me for technical support. DISCLAIMER: The views
expressed in this posting are mine, and do not necessarily reflect the
views of my employer. Thank you.
Phillip Pi
>> Since I had to dump Debian's IceApe a few weeks ago, I had to install
>> SeaMonkey (SM) v1.1.4 from
>> seamonkey-1.1.14.en-US.linux-i686.installer.tar.gz into
>> /home/Programs/seamonkey/ ... Mostly everything works, but I noticed
>> saving files cause SM to freeze hard. CPU usage is in used from SM.
>>
>> I have to kill its three processes through KDE v3.5.10's terminal since
>> regular kills weren't enough. At first, I thought it was the old
>> SessionSaver extension but I was still able to reproduce the freeze. I
>>
>> I tried to use strace but it seems to stop when SM loads a Web page and
>> doesn't output anymore.
>>
>> Any ideas? Thank you in advance. :)
>
> Use the -debug command line switch.
>
> seamonkey -debug
I will try that later on my local machine (don't want to do it over
SSH). Weird that I didn't see -debug listed:
$ ./seamonkey --help
Usage: ./seamonkey-bin [ options ... ] [URL]
where options include:
X11 options
--display=DISPLAY X display to use
--sync Make X calls synchronous
--no-xshm Don't use X shared memory extension
--xim-preedit=STYLE
--xim-status=STYLE
--g-fatal-warnings Make all warnings fatal
SeaMonkey options
-height <value> Set height of startup window to <value>.
-h or -help Print this message.
-installer Start with 4.x migration window.
-width <value> Set width of startup window to <value>.
-v or -version Print ./seamonkey-bin version.
-CreateProfile <profile> Create <profile>.
-P <profile> Start with <profile>.
-ProfileWizard Start with profile wizard.
-ProfileManager Start with profile manager.
-SelectProfile Start with profile selection dialog.
-UILocale <locale> Start with <locale> resources
as UI Locale.
-contentLocale <locale> Start with <locale> resources
as content Locale.
-remote <command> Execute <command> in an already running
SeaMonkey process. For more info, see:
http://www.mozilla.org/unix/remote.html
-splash Enable splash screen.
Also, how can I output the debug into a log file if they are shown on
screen?
Ant
> Use the -debug command line switch.
>
> seamonkey -debug
$ ./seamonkey --debug
./run-mozilla.sh -g ./seamonkey-bin
MOZILLA_FIVE_HOME=.
LD_LIBRARY_PATH=.:./plugins:/usr/local/lib/mre/mre-1.1.14
DISPLAY=:0.0
DYLD_LIBRARY_PATH=.:/usr/local/lib/mre/mre-1.1.14
LIBRARY_PATH=.:./components:/usr/local/lib/mre/mre-1.1.14
SHLIB_PATH=.:/usr/local/lib/mre/mre-1.1.14
LIBPATH=.:/usr/local/lib/mre/mre-1.1.14
ADDON_PATH=.
MOZ_PROGRAM=./seamonkey-bin
MOZ_TOOLKIT=
moz_debug=1
moz_debugger=
/usr/bin/gdb ./seamonkey-bin -x /tmp/mozargs.wodAef
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
(gdb)
Now what? I don't know how to use this gdb thing. :(
--
"When an ant gets wings, it loses its head." --Bosnian Proverb
Ant
> I don't know from SeaMonkey but I installed Firefox in Ubuntu once and
> it did exactly the same thing.
> Yahoo maps blew up the version from the repos so I installed a 'newer'
> release.
> Popups like download manager took forever to popup then hung forever
> when downloading.
> Turned out, I had grabbed a beta from the FTP site.
> Installed the release version and everything worked fine.
The one I got is: 14679286 2008-12-05 01:26
seamonkey-1.1.14.en-US.linux-i686.installer.tar.gz
I hope that's the right one to use for Debian.
--
"When many work together for a goal, great things may be accomplished.
It is said a lion cub was killed by a single colony of ants." --Saskya
Pandita
clay
Install the debug package maybe? I dunno...
clay
> On 3/16/2009 3:05 PM PT, clay typed:
>
>> I don't know from SeaMonkey but I installed Firefox in Ubuntu once and
>> it did exactly the same thing.
>> Yahoo maps blew up the version from the repos so I installed a 'newer'
>> release.
>> Popups like download manager took forever to popup then hung forever
>> when downloading.
>> Turned out, I had grabbed a beta from the FTP site.
>> Installed the release version and everything worked fine.
>
> The one I got is: 14679286 2008-12-05 01:26
> seamonkey-1.1.14.en-US.linux-i686.installer.tar.gz
>
> I hope that's the right one to use for Debian.
I don't know which would be correct for Debian. Might search the Debian
list.
There are versions up to 2.0 on the FTP site.
<ftp://ftp.mozilla.org/pub/seamonkey/releases/2.0a3/seamonkey-2.0a3.en-US.linux-i686.tar.bz2>
Phillip Pi
Which one? I am not familiar with this one.
Phillip Pi
>> The one I got is: 14679286 2008-12-05 01:26
>> seamonkey-1.1.14.en-US.linux-i686.installer.tar.gz
>>
>> I hope that's the right one to use for Debian.
>
> I don't know which would be correct for Debian. Might search the Debian
> list.
> There are versions up to 2.0 on the FTP site.
> <ftp://ftp.mozilla.org/pub/seamonkey/releases/2.0a3/seamonkey-2.0a3.en-US.linux-i686.tar.bz2>
Just remember, Debian dropped IceApe (basically SeaMonkey) so I have to
use Mozilla's SeaMonkey. :(
clay
oops...
If you install from source the debug package wouldn't be of much use.
apps in the repositories (is that what they call them in Debian?) have
other packages available for install. debug, help files, etc.
I only ran Debian for a couple hours so I'm not up on the jargon.
Probably, you'd have to compile with debugging enabled.
clay
> On 3/17/2009 9:11 AM PT, clay wrote:
>
>>> The one I got is: 14679286 2008-12-05 01:26
>>> seamonkey-1.1.14.en-US.linux-i686.installer.tar.gz
>>>
>>> I hope that's the right one to use for Debian.
>>
>> I don't know which would be correct for Debian. Might search the
>> Debian list.
>> There are versions up to 2.0 on the FTP site.
>> <ftp://ftp.mozilla.org/pub/seamonkey/releases/2.0a3/seamonkey-2.0a3.en-US.linux-i686.tar.bz2>
>
>
> Just remember, Debian dropped IceApe (basically SeaMonkey) so I have to
> use Mozilla's SeaMonkey. :(
You really should visit linux.debian.user and sign up to their mailing
list. Lots of activity there.
Probably this has already been solved by others.
Jens Hatlak
> (no debugging symbols found)
> (gdb)
>
> Now what? I don't know how to use this gdb thing. :(
I don't know much more there either but the next step should be entering
"run". Then, for crash bugs, the next command after that would be "bt"
for getting a backtrace. Since in your case SM freezes I don't know
whether killing SM will give you similar results but you may try
pressing Ctrl+C in the console window instead of killing SM by other
means. Anyway, as the "(no debugging symbols found)" indicates, your SM
is stripped so you probably won't get meaningful results anyway. You'd
have to use a version compiled with debugging support but I'm not sure
whether those are available or you need to compile yourself. If you
installed SM using packages for your distribution it may be worth a try
to search for a matching package providing debugging symbols.
There are some instructions on [1] but I guess they don't apply to SM1.x.
[1]
<https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report>
HTH
Jens
--
Jens Hatlak <http://jens.hatlak.de/>
SeaMonkey Trunk Tracker <http://smtt.blogspot.com/>
Phillip Pi
> Ant wrote:
>> (no debugging symbols found)
>> (gdb)
>>
>> Now what? I don't know how to use this gdb thing. :(
>
> I don't know much more there either but the next step should be entering
> "run". Then, for crash bugs, the next command after that would be "bt"
> for getting a backtrace. Since in your case SM freezes I don't know
> whether killing SM will give you similar results but you may try
> pressing Ctrl+C in the console window instead of killing SM by other
> means. Anyway, as the "(no debugging symbols found)" indicates, your SM
> is stripped so you probably won't get meaningful results anyway. You'd
> have to use a version compiled with debugging support but I'm not sure
> whether those are available or you need to compile yourself. If you
> installed SM using packages for your distribution it may be worth a try
> to search for a matching package providing debugging symbols.
Thanks. Yeah, I can't find any Debian packages for SeaMonkey and Debian
dropped IceApe that is another name for SeaMonkey.
Oh well. I think my next plan is to try a new profile. Does anyone know
how to launch that under Linux like in Windows?
Phillip Pi
>> Just remember, Debian dropped IceApe (basically SeaMonkey) so I have
>> to use Mozilla's SeaMonkey. :(
>
> You really should visit linux.debian.user and sign up to their mailing
> list. Lots of activity there.
> Probably this has already been solved by others.
I doubt it. Thwy only handled IceApe, not SeaMonkey. They willprobably
ask Mozilla guys. :)
Ant
change anything! Maybe apt-get update and upgrade changed something
recently. I will follow-up if it happens again. Computers are strange!
--
"It doesn't matter what your D&D manual says, you did not get 5
experience points for killing the giant ant in your kitchen." --BBspot's
Geek Horoscopes (7/30/2004)