Closed
Bug 11311
Opened 25 years ago
Closed 25 years ago
[PP]Nightly build stops working after initial uses (24 hours?).
Categories
(SeaMonkey :: General, defect, P3)
Tracking
(Not tracked)
People
(Reporter: jdalbec, Assigned: don)
References
()
Details
After the first few uses, the 8/3/99 nightly build hangs with the message:
nsComponentManager: Load(libappcores.so) FAILED with error: /home/john/tgzfiles/
mozilla/package/libappcores.so: undefined symbol: SetScriptObject__13nsBaseAppCo
rePv
followed by:
Creating browser app core
JavaScript error: BrowserAppCore is not defined
URL: file:////home/john/tgzfiles/mozilla/package/chrome/navigator/content/defaul
t/navigator.xul LineNo: 29
Gdk-ERROR **: an x io error occurred
aborting...
Summary: Nightly build stops working after initial uses (24 hours?). → [PP]Nightly build stops working after initial uses (24 hours?).
Yes, I've tested this only with RH 5.2.
I'm still waiting for another nightly build that doesn't crash on startup.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 4•25 years ago
|
||
verified dup
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•