Closed Bug 9963 Opened 26 years ago Closed 26 years ago

Locking logic is wrong while in standalone mode

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: dougt, Assigned: dveditz)

Details

When the XPInstall engine is used in blocking mode: http://lxr.mozilla.org/seamonkey/source/xpinstall/src/nsSoftwareUpdateRun.cpp#2 77 the PR_LOCK fail in RunNextInstall() because the same thread will try to obtain the lock in a circular manner.
Assignee: dougt → dveditz
Flags of 1 means "force mode" so I fail to see why that determines whether we spawn a thread or not -- that's probably a bug/test-hack. We should always spawn a thread, or invent a new flag and bitmask to see the result. But if running on the same thread is something you want to do for some reason we could fix the locking order in RunNextInstall() (add several PR_Unlock()s instead of one at the end). I'll take this one.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Target Milestone: M9
This will be and only can be verified when the install wizard uses xpinstall to install xpis.
Status: RESOLVED → VERIFIED
Build 9/24/99 This installer appears to install properly. Marking Verified.
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.