Open Bug 44808 Opened 25 years ago Updated 3 years ago

make chrome registry thread safe

Categories

(Core :: XUL, defect, P3)

Product:
Core
Component:
XUL
Type:
defect

Tracking

()

Milestone:
Future

People

(Reporter: waterson, Unassigned)

References

Details

(Keywords: arch, embed, Whiteboard: [nsbeta2-])

Per bug 42107, we need to make the chrome registry threadsafe.
Blocks: 42107
Keywords: arch
Nominating for nsbeta2 due to dependencies.
Status: NEW → ASSIGNED
Keywords: nsbeta2
Putting on [nsbeta2-] radar. Not critical to beta2. If Judson's group has a fix for this, he can approve a checkin for this.
Keywords: embed
Whiteboard: [nsbeta2-]
jud: is this still an issue for embedding? if not, i'm gonna push it out to mfuture...
it is still a problem. it's downright embarassing. part of our "init" process requires the embeddor to initialize string bundles before doing anything else. Can we go back to ruslans late init approach in 42107?
No, we can't, but I'm working on a fix as we speak (type).
Target Milestone: --- → Future

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.

Assignee: waterson → nobody
Status: ASSIGNED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.