Closed
Bug 8971
Opened 27 years ago
Closed 27 years ago
Thread spawned by XPInstall causes crash on startup
Categories
(Core Graveyard :: Installer: XPInstall Engine, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
M8
People
(Reporter: samir_bugzilla, Assigned: samir_bugzilla)
Details
Currently, XPInstall spawns a thread at startup to perform scheduled tasks
including file deletions/replacements from previously conducted installs. This
causes a crash because
"...of a race condition in the dynamic loader. Two threads are
trying to relocate code at the same time and this royally hoses stuff. Thread #1
is running the component manager. Evil Thread #2 comes from normal static
linkage from xpinstall." [waterson, bug #8849]
As a result XPInstall has been turned of on Unix again.
| Assignee | ||
Updated•27 years ago
|
Priority: P3 → P1
| Assignee | ||
Updated•27 years ago
|
Status: NEW → RESOLVED
Closed: 27 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 1•27 years ago
|
||
Fix checked in yesterday afternoon; today's build should reflect this. XPInstall
has been re-enabled on the Unices.
| Assignee | ||
Updated•27 years ago
|
Target Milestone: M8
| Assignee | ||
Comment 2•27 years ago
|
||
Proposed verification per QA request:
Repeated launching of apprunner on multiple machines with RedHat 5.2 (stock
install is Linux kernel 2.0.36 and old glibc). This bug was due to a race
condition at component load-time (apprunner start-time) and thus is hard to
verify.
Build 7/9/99
No known problems. New bug report will be prepared if new or similar symptoms
arise.
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall
Engine
Updated•10 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•