228227 - Tbird/2 v0.4 fails to start when "mozturbo.exe" and/or "mozilla.exe" are running.

Status: RESOLVED INVALID

(Thunderbird :: Mail Window Front End, defect)

Description

[Austy Garhi]

User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4; en-US; rv:1.4.1) Gecko/20031010
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4; en-US; rv:1.4.1) Gecko/20031010

Error box pops up, and POPUPLOG.OS2 captures error:
"12-11-2003  09:29:25  SYS2070  PID 010a  TID 0001  Slot 0076
C:\USOF\THUNDERBIRD\THUNDERBIRD.EXE
THUNDERBIRD->XPCOM.4258
182"

Error happens despite having previously set up the environment as:
MOZILLA_HOME=C:\USOF\THUNDERBIRD
BEGINLIBPATH=C:\USOF\THUNDERBIRD
LIBPATHSTRICT=T
MOZ_NO_REMOTE=1


Reproducible: Always

Steps to Reproduce:
1. Start "mozilla.exe"
2. Start "thunderbird.exe"
3. Read error message.
4. Close error box.
5. Shutdown "mozilla.exe"
6. Have a cup of coffee.
7. Start "mozturbo.exe"
8. Start "thunderbird.exe"
9. Read error box.

Actual Results:  
Error box pops up, and POPUPLOG.OS2 captures error:
"12-11-2003  09:29:25  SYS2070  PID 010a  TID 0001  Slot 0076
C:\USOF\THUNDERBIRD\THUNDERBIRD.EXE
THUNDERBIRD->XPCOM.4258
182"

Expected Results:  
Start up.

Comment 1

[Austy Garhi]

Tbird/2 v0.4 refuses to start also when Fbird/2 v0.7 is running.  And viceversa.

POPUPLOG.OS2 entry:
12-12-2003  13:51:14  SYS3175  PID 063f  TID 0001  Slot 0099
C:\USOF\THUNDERBIRD\THUNDERBIRD.EXE
c0000005
1dc51382
P1=00000001  P2=0001fffc  P3=XXXXXXXX  P4=XXXXXXXX
EAX=0011ff84  EBX=0011fdac  ECX=00008000  EDX=0011ff84
ESI=0001fffc  EDI=002da6bc
DS=0053  DSACC=d0f3  DSLIM=1fffffff
ES=0053  ESACC=d0f3  ESLIM=1fffffff
FS=150b  FSACC=00f2  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1dc51382  CSACC=d0df  CSLIM=1fffffff
SS:ESP=0053:0011fd74  SSACC=d0f3  SSLIM=1fffffff
EBP=0011fe28  FLG=00012606

LIBC04.DLL 0001:00001382

Comment 2

[mhlx.os2]

Here is what my Warpzilla Branch 1.4.1 says:

Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4.1) Gecko/20031014

Branch 1.4.1 + Thunderbird 0.4 (original) -> WFM
Branch 1.4.1 + Thunderbird 0.4 (updated) -> WFM

Note that my 1.4.1 says 20031014 but yours says 20031010 (maybe 1.4.1 was
updated and it is not listed on the Warpzilla page at
http://www.mozilla.org/ports/os2/ ), but maybe that is not the problem.


I think the problem is mine says Warp 4.5 , yours says Warp 4 .  That "<mozilla
or thunderbird, etc>->XPCOM.<number>" error says OS/2 is loading the wrong DLL
version (the one already loaded instead of loading the correct one).

I am running Warp 4 + FP15 + testcase kernel 14.096e_W4 (W420031113).  What
Fixpak are you running?  You may need one of the newer ones that supports
LIBPATHSTRICT .  I'm not sure which FP or kernel was the first to support
LIBPATHSTRUCT .

Comment 3

[Sachin]

I also see the same result as comment #2. 
We could see the same trap while running thunderbird 0.4 after running mozilla
1.4.1. Setting the following environment variables resolves the problem.

SET LIBPATHSTRICT=T
SET BEGINLIBPATH=C:\THUNDERBIRD;%BEGINLIBPATH% (takes the xpcom.dll in
c:\thunderbird directory)

Comment 4

[Austy Garhi]

From the OS/2 Command Reference: "BEGINLIBPATH is not actually part of the
environment."

From comment #3 above:
"SET BEGINLIBPATH=C:\THUNDERBIRD;%BEGINLIBPATH% (takes the xpcom.dll in
c:\thunderbird directory)"

the resultant string for BEGINLIBPATH then would be:

C:\THUNDERBIRD;____ <--nothing there, because there is no prior  contents for
it, BEGINLIBPATH does not exist in the environment previously.

I don't see how  such should make a difference  . . . in fact, it did not make a
difference here: Tbird still crashed with a  SYS2070 error:

12-16-2003  19:36:11  SYS2070  PID 0118  TID 0001  Slot 0082
C:\USOF\THUNDERBIRD\THUNDERBIRD.EXE
THUNDERBIRD->XPCOM.4258
182

And let's remember, I have been setting BEGINLIBPATH to Tbird's root dir all
along AND for the session for the Tbird process: if I may quote my above posted
description of the bug:
"
Error happens despite having previously set up the environment as:
MOZILLA_HOME=C:\USOF\THUNDERBIRD
BEGINLIBPATH=C:\USOF\THUNDERBIRD
LIBPATHSTRICT=T
MOZ_NO_REMOTE=1
"

Comment 5

[Steve Wendt]

Austy, BEGINLIBPATHSTRICT=T only works on recent kernels.  Since you have Warp
4.0 rather than Warp 4.5, you can't use it (FixPak 15 is a free update to Warp
4.5, you might want to get it).

Comment 6

[Austy Garhi]

OK, here's what I've done:
--applied fixpak 15
--installed "December 11, 2003 The Thunderbird 0.4 release was missing a patch
for the customize crash. A new zip with the fix has been uploaded."
--had already installed LIBC04FIX1.ZIP
--environment is set up as:

LIBPATHSTRICT=T
BEGINLIBPATH=C:\USOF\THUNDERBIRD
MOZ_NO_REMOTE=1

--Same environment for FIREbird, with its own appropriate path.
--I launch Firebird 0.7 first; after it has fully started, I launch Tbird 0.4,
and this results:

12-19-2003  19:30:48  SYS3175  PID 007f  TID 0001  Slot 009d
C:\USOF\THUNDERBIRD\THUNDERBIRD.EXE
c0000005
1d721382
P1=00000001  P2=0001fffc  P3=XXXXXXXX  P4=XXXXXXXX
EAX=0011ff84  EBX=0011fdac  ECX=00008000  EDX=0011ff84
ESI=0001fffc  EDI=002d9b1c
DS=0053  DSACC=d0f3  DSLIM=3fffffff
ES=0053  ESACC=d0f3  ESLIM=3fffffff
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1d721382  CSACC=d0df  CSLIM=3fffffff
SS:ESP=0053:0011fd74  SSACC=d0f3  SSLIM=3fffffff
EBP=0011fe28  FLG=00012606

LIBC04.DLL 0001:00001382

Still HORKED: Tbird won't fly while any other bird or lizard is flying.

Comment 7

[Steve Wendt]

Austy, you say: "environment is set up as" - this is a little ambiguous.  The
LIBPATH stuff aren't "real" environment variables, and have to be set up in the
specific session that you launch the app.  Are you using a CMD file that sets
this up, or are you using a different (unlikely to work) method?

Comment 8

[Austy Garhi]

"> Austy, you say: "environment is set up as" - this is a little ambiguous.  
OK: the ACTIVE environment in the ACTIVE session where the app is launched.
, , ,
"> Are you using a CMD file that sets this up, or are you using a different
"> (unlikely to work) method?
I'm using 2 .CMD files: 1 for Firebird, and 1 for Thunderbird.
[George Costanza's father: "It's horked, horked I tell ya."  (hah hah ;)  )

Let's not forget the problem we have here: Tbird/2 v0.4 is REDEFINING the stated
goal in http://www.mozilla.org/projects/thunderbird/: "Our intended customer is
someone who uses Mozilla Firebird (or another stand alone browser) as their
primary browser and wants a mail client based on mozilla that "plays nice" with
the browser."  Because Tbird is refusing to "play nice" with Fbird . . . and
with Moz 1.4.1.  ;>

Comment 9

[Austy Garhi]

I bet the following is related:
"mozilla.exe -mail" fails to start if Firebird/2 v0.7 is running. Error from
POPUPLOG.OS2:
12-21-2003  13:39:57  SYS2070  PID 0063  TID 0001  Slot 0077
D:\USOF\MOZILLA\MOZILLA.EXE
MOZILLA->PLC4.PL_strcasecmp
127
SYS0127: The specified procedure could not be found.

Comment 10

[Mike Kaply [:mkaply]]

This is exactly what is expected. They use the same DLL names so you can only
run concurrent versions if they are based on exactly the same Mozilla code.

This is the way things are right now until we get all TB/FB/Mozilla releases
from the same base.

If your kernel doesn't support LIBPATHSTRICT, there is no workaround for this.