Closed Bug 10707 Opened 27 years ago Closed 27 years ago

browser hanging when using NSPR threads

Categories

(NSPR :: NSPR, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 11925

People

(Reporter: jim_nance, Assigned: don)

Details

If I build apprunner under Red Hat 6.0 using NSPR threads instead of pthreads, apprunner will hang after printing: GFX: dpi=96 t2p=0.0666667 p2t=15 depth=16 Using '/usr/local/home/jlnance/src/19980429/nbt/dist/bin' as the resource: base ProfileName : mozProfile ProfileDir : /usr/local/home/jlnance/.mozilla/mozProfile Got the event queue from the service Calling gdk_input_add with event queue gdb indicates that it is sitting in poll() This is not too much of a problem under Linux, where pthreads are available, but the same thing happens under HP-UX 10.20, which does not have pthreads, and it is a real problem there. Incidently the linux machine was configured using --with-necko and the HP machine was not using --with-necko so it does not seem to have anything to do with this library.
Component: Browser-General → NSPR
Product: Browser → NSPR
QA Contact: leger → srinivas
Version: other → 3.0
Sending over to NSPR folks to comment.
There isn't enough information here to know what the problem might be. Some things you can do - get a trace stack - trace the system calls to see if the application is making any system calls - if the apprunner is linked with Motif or some other GUI library you should check to see if the apprunner has ever been tested in such a manner
I'm not convinced NSPR is the culprit in this case. Earlier, I built using the m8 source and later using the tag, PRE_NECKO_LANDING_M9_MidLifeCrisis_19990728_BASE. In both cases, apprunner brought up a window w/o a problem. I also did a diff between the PRE tag and the current source. Outside of a Linux.mk and pr/tests/Makefile tweaks, NSPR hasn't changed.
Ok, I screwed up. I thought --enable-necko was post M8 & M8.5. When I built mozilla M8 using --without-pthreads --enable-necko, it hung in the same spot as it does with the current source.
Status: NEW → RESOLVED
Closed: 27 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 11925 ***
Status: RESOLVED → VERIFIED
verified dup...see Bug 11925
You need to log in before you can comment on or make changes to this bug.