Closed Bug 33329 Opened 25 years ago Closed 25 years ago

mozilla hangs when start-psm fails

Categories

(Core Graveyard :: Security: UI, defect, P3)

1.0 Branch
x86
Linux
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: dmosedale, Assigned: ddrinan0264)

Details

(Whiteboard: [nsbeta2-][from mwelch@netscape.com])

Attachments

(1 file)

Red Hat Linux build from the tip: --enable-x11-shm --enable-optimize --disable-debug CFLAGS="-g" When start-psm fails, the browser hangs completely. It should instead fail gracefully and continue to work so that data and session info in other windows is not lost.
dmose, did you have psm installed? did a dialog every appear asking you for the location of psm? Did you see anything appear in the console? Specifically "*** Failure setting up Cartman! \n"
I did have it installed, and start-psm was executing, but psm itself was failing because of a dynamic-linking problem. bug 33331 contains more info about the specific problem.
And no, a dialog did not appear, because it had already found {start-,}psm, and the only thing on stderr was related to the dynamic linking error after fstat() not being found in libnspr3.so.
dmose, just to reiterate, you did install psm via xpinstall? It might be a problem with the cmt client lib's CMT_EstablishControlConnection() call. Attached is a diff that fixes(?) a couple problems. a) Instead of calling system(), it might be better to call nspr's PR_CreateProcessDetached() b) it removes the wait after launch code (which looked wrong for unix) and just does exactly what the comment states "Now try to connect to the psm server. We will try to connect a maximum of 30 times and then give up." dmose, could you try this diff? Mark can you review/comment on this diff?
I'm concerned about this diff as written, because it creates a dependency on NSPR within the PSM client library itself. How hard would it be to move the NSPR bits into a separate routine, such as we do now with the socket, read/write, etc. methods? Perhaps a Launch method?
Oh, sure. I didn't think about that dependancy. dmose, could you just apply the patch which removes the unix specify wait while launch code to see if that does it? mark, maybe it is better if I just launch psm from my code and not use EstablishControlConnection?
Yes, I used XPinstall. Applying just that part of the patch brings up a new error: /mozilla-bin: error in loading shared libraries: /u/dmose/s/browser-main/mozilla/obj-i686-pc-linux-gnu/dist/bin/libcmt.so: undefined symbol: Sleep The place I see Sleep() defined is as part of nsIThreadManager which is from the OJI world.
Assignee: dougt → mwelch
Whiteboard: [from mwelch@netscape.com]
I'm leaving Netscape, so I'm reassigning all my pending bugs to David Drinan. I've added "[from mwelch@netscape.com]" to the status whiteboard for each of these bugs for easier searching.
Assignee: mwelch → ddrinan
Setting milestone to M16.
Keywords: nsbeta2
Target Milestone: --- → M16
PDT would like to know how likely a user is to see start-psm fail before making a +/- call for nsbeta2
Whiteboard: [from mwelch@netscape.com] → [NEED INFO] [from mwelch@netscape.com]
Putting on [nsbeta2-] radar. Not critical to beta2. Putting on nsbeta3 radar for a lookee then :-)
Keywords: nsbeta3
Whiteboard: [NEED INFO] [from mwelch@netscape.com] → [nsbeta2-][from mwelch@netscape.com]
M16 has been out for a while now, these bugs target milestones need to be updated.
Marking worksforme. I haven't seen this problem.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Verified.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: M16 → ---
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: