eSeaMonkey 1.1.3 crash - OS2

This is a discussion on eSeaMonkey 1.1.3 crash - OS2 ; When I arrived in the office this morning I found my system appeared to be frozen. I hit ctl-esc and after a bit a pop-up about a problem eSeaMonkey (which disappeared after I hit ctl-esc) and only a "Close" button ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: eSeaMonkey 1.1.3 crash

  1. eSeaMonkey 1.1.3 crash

    When I arrived in the office this morning I found my system appeared to be
    frozen. I hit ctl-esc and after a bit a pop-up about a problem eSeaMonkey
    (which disappeared after I hit ctl-esc) and only a "Close" button came up,
    so I clicked it. I found a pop-up log entry:

    >09-04-2007 22:12:51 SYS3170 PID 0060 TID 0001 Slot 00dc
    >J:\OS2-APPS\SEAMONKEY-1.1.3\SEAMONKEY.EXE
    >0000007f
    >00000000
    >EAX=01228006 EBX=8000150b ECX=00010060 EDX=13e8af00
    >ESI=3ba03740 EDI=1260a150
    >DS=0053 DSACC=f0f3 DSLIM=ffffffff
    >ES=0053 ESACC=f0f3 ESLIM=ffffffff
    >FS=150b FSACC=00f3 FSLIM=00000030
    >GS=0000 GSACC=**** GSLIM=********
    >CS:EIP=005b:1e992325 CSACC=f0df CSLIM=ffffffff
    >SS:ESP=0053:0011ff48 SSACC=f0f3 SSLIM=ffffffff
    >EBP=00000000 FLG=00212206


    and the following output from SeaMonkey:

    >Killed by SIGSEGV
    >pid=0x0060 ppid=0x0022 tid=0x0001 slot=0x00dc pri=0x0200 mc=0x0001
    >J:\OS2-APPS\SEAMONKEY-1.1.3\SEAMONKEY.EXE
    >XPCOMCOR 0:00041c54
    >cs:eip=005b:1d761c54 ss:esp=0053:0011fce4 ebp=0011fcec
    > ds=0053 es=0053 fs=150b gs=0000 efl=00012287
    >eax=00000054 ebx=00000001 ecx=00000000 edx=2259fe24 edi=20032db8
    >esi=2259fe20 Process dumping was disabled, use DUMPPROC / PROCDUMP to
    >enable it. RWSCLI08: RwsExitListProc - termination code= 0


    The timestamp of the POPUPLOG entry matches what my clock read when I came
    in this morning and the timestamp of the SeaMonkey output shows it
    occurred this morning when I hit ctl-esc.

    What happened here? Can I avoid it in the future? I have also seen
    update messages for SeaMonkey 1.1.4, but have been waiting for Peter to
    release his updated build. Any possibility 1.1.4 fixes this?

    -- Dave
    -----------------------------------------------------------
    dhdurgeeverizonnet
    -----------------------------------------------------------


  2. Re: eSeaMonkey 1.1.3 crash

    On Wed, 5 Sep 2007 10:42:03 UTC, me@privacy.net wrote:

    > >J:\OS2-APPS\SEAMONKEY-1.1.3\SEAMONKEY.EXE
    > >XPCOMCOR 0:00041c54
    > >cs:eip=005b:1d761c54 ss:esp=0053:0011fce4 ebp=0011fcec
    > > ds=0053 es=0053 fs=150b gs=0000 efl=00012287
    > >eax=00000054 ebx=00000001 ecx=00000000 edx=2259fe24 edi=20032db8
    > >esi=2259fe20 Process dumping was disabled, use DUMPPROC / PROCDUMP to
    > >enable it. RWSCLI08: RwsExitListProc - termination code= 0

    >
    > The timestamp of the POPUPLOG entry matches what my clock read when I came
    > in this morning and the timestamp of the SeaMonkey output shows it
    > occurred this morning when I hit ctl-esc.
    >
    > What happened here? Can I avoid it in the future? I have also seen
    > update messages for SeaMonkey 1.1.4, but have been waiting for Peter to
    > release his updated build. Any possibility 1.1.4 fixes this?


    My new release will be 1.1.5 but it's unlikely to be fixed because I
    don't know what caused it. The crash address points to code which is
    _very_ unlikely to go wrong. (PL_RevokeEvents in case anybody else is
    interested.)
    --
    Greetings, | My From: address is valid as is the version without "spam"
    Peter. | I try to find real messages among the spam once a week

  3. Re: eSeaMonkey 1.1.3 crash

    In , on 09/06/2007
    at 11:11 PM, "Peter Weilbacher" said:

    >On Wed, 5 Sep 2007 10:42:03 UTC, me@privacy.net wrote:


    >> >J:\OS2-APPS\SEAMONKEY-1.1.3\SEAMONKEY.EXE
    >> >XPCOMCOR 0:00041c54
    >> >cs:eip=005b:1d761c54 ss:esp=0053:0011fce4 ebp=0011fcec
    >> > ds=0053 es=0053 fs=150b gs=0000 efl=00012287
    >> >eax=00000054 ebx=00000001 ecx=00000000 edx=2259fe24 edi=20032db8
    >> >esi=2259fe20 Process dumping was disabled, use DUMPPROC / PROCDUMP to
    >> >enable it. RWSCLI08: RwsExitListProc - termination code= 0

    >>
    >> The timestamp of the POPUPLOG entry matches what my clock read when I came
    >> in this morning and the timestamp of the SeaMonkey output shows it
    >> occurred this morning when I hit ctl-esc.
    >>
    >> What happened here? Can I avoid it in the future? I have also seen
    >> update messages for SeaMonkey 1.1.4, but have been waiting for Peter to
    >> release his updated build. Any possibility 1.1.4 fixes this?


    >My new release will be 1.1.5 but it's unlikely to be fixed because I
    >don't know what caused it. The crash address points to code which is
    >_very_ unlikely to go wrong. (PL_RevokeEvents in case anybody else is
    >interested.)


    Does the popuplog.os2 entry I posted give any clue? As I noted in my
    original post I believe that is where the problem originated, as when I
    arrived in the morning that was the time the clock still read and I found
    the system non-responsive until ctl-esc precipitated the crash you see
    above. Here is the popuplog.os2 entry again:

    >09-04-2007 22:12:51 SYS3170 PID 0060 TID 0001 Slot 00dc
    >J:\OS2-APPS\SEAMONKEY-1.1.3\SEAMONKEY.EXE
    >0000007f
    >00000000
    >EAX=01228006 EBX=8000150b ECX=00010060 EDX=13e8af00
    >ESI=3ba03740 EDI=1260a150
    >DS=0053 DSACC=f0f3 DSLIM=ffffffff
    >ES=0053 ESACC=f0f3 ESLIM=ffffffff
    >FS=150b FSACC=00f3 FSLIM=00000030
    >GS=0000 GSACC=**** GSLIM=********
    >CS:EIP=005b:1e992325 CSACC=f0df CSLIM=ffffffff
    >SS:ESP=0053:0011ff48 SSACC=f0f3 SSLIM=ffffffff
    >EBP=00000000 FLG=00212206



    --
    -----------------------------------------------------------
    dhdurgeeverizonnet
    -----------------------------------------------------------


+ Reply to Thread