Open Bug 701427 Opened 13 years ago Updated 3 months ago

Compartment checking assertions tolerate a NULL cx->compartment

Categories

(Core :: JavaScript Engine, task, P3)

Product:
Core
Component:
JavaScript Engine
Platform:
x86
macOS
Type:
task

Tracking

()

People

(Reporter: bhackett1024, Unassigned)

References

(Blocks 1 open bug)

Details

CompartmentChecker does this weird thing where if cx->compartment is NULL then it only checks that the compartments of the various things are all consistent with each other. Most of the API functions thus tolerate being passed a cx with a NULL compartment. There are places in the browser that have such behavior, which looks broken to me.
Assignee: general → nobody
Severity: normal → S3

These days we have this code, which does seem to do similar. Unsure of how important that behaviour is, but probably worth looking into. I am unsure when a null compartment would happen.

Blocks: sm-api
Severity: S3 → N/A
Type: defect → task
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.