Closed Bug 417501 Opened 17 years ago Closed 15 years ago

threadsafety hazard for parallel lookup on dense arrays

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: shaver, Unassigned)

References

Details

(This bug doesn't exist on trunk until I land bug 322889, but I need a bug number assigned for a FIXME.) array_lookupProperty uses a per-object pigeonhole (JSSLOT_ARRAY_LOOKUP_HOLDER) for storing the active property for a lookup. If two threads race to perform a lookup, one could stomp the other right in the pigeonhole. If a given context can only have a single lookup "in flight" at a time, then we could move the pigeonhole to the context for even greater memory savings (after we fix bug 408416, if that bug's fix doesn't obviate this entire pattern).
Summary: threadsafety hazard for parallel lookup on dense arrrays → threadsafety hazard for parallel lookup on dense arrays
Depends on: 419537
Fixed by bug 487930. /be
Status: NEW → RESOLVED
Closed: 15 years ago
Depends on: 487930
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.