Closed Bug 402352 Opened 17 years ago Closed 8 years ago

XRemoteClient ctor does not initialize mMozCommandLineAtom

Categories

(Core Graveyard :: X-remote, defect)

Product:
Core Graveyard
Component:
X-remote
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
trivial

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: tom, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9a9pre) Gecko/2007110300 Minefield/3.0a9pre
Build Identifier: 

widget/src/xremoteclient/XRemoteClient.cpp, ctor is around line 87. Found while trying to understand the code. Do I need to post a patch? It's a simple one-line change..

Reproducible: Always
Assignee: blizzard → gtk
Mass resolving a bunch of old bugs in the x-remote component in preparation for archiving it. If this bug is still valid and useful, please move it to the "Toolkit: Startup and Profile System" component and reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Gecko has a two-stage initialization process and this was initialized in Init(), but the double initialization was added anyway in
https://hg.mozilla.org/mozilla-central/rev/5f773a189557
Depends on: 1231378
Resolution: INCOMPLETE → INVALID
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.