Closed
Bug 1441290
Opened 6 years ago
Closed 6 years ago
Eliminate the static atom table
Categories
(Core :: XPCOM, enhancement)
Core
XPCOM
Tracking
()
RESOLVED
DUPLICATE
of bug 529808
People
(Reporter: bholley, Unassigned)
Details
(Whiteboard: [MemShrink])
This weighs 65k per content process (ignoring the atoms themselves, which live in the binary). Static atoms also live in the main table, so I think the only reason this was added was to support off-main-thread static atom access for the HTML parser (bug 514661). However, we now have a threadsafe atom table, and I'm making it faster in bug 1440824. I'll bet we can drop this table and replace the consumers with a special API that does lookups on the primary table.
Reporter | ||
Updated•6 years ago
|
Blocks: memshrink-content
Updated•6 years ago
|
Whiteboard: [MemShrink]
Comment 1•6 years ago
|
||
Already filed as bug 529808. I have done various bits of prep work for this. It should be not too hard now.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
No longer blocks: memshrink-content
You need to log in
before you can comment on or make changes to this bug.
Description
•