Open Bug 1251722 Opened 8 years ago Updated 2 years ago

WorkerPrivate::Freeze/Thaw are called with null windows from sharedworker code but comments say that can't happen

Categories

(Core :: DOM: Workers, defect, P5)

defect

Tracking

()

Tracking Status
firefox47 --- affected

People

(Reporter: bzbarsky, Unassigned)

Details

(Whiteboard: btpp-followup-2016-03-11)

See bug 1251045 comment 12.  

The passing of null goes all the way back to 643325, which is when the window argument was added.

The comment claiming null can't be passed goes back to bug 1092102.  So I think the comment is more likely to be wrong.
Flags: needinfo?(ejpbruel)
Whiteboard: btpp-followup-2016-03-04
(In reply to Boris Zbarsky [:bz] from comment #0)
> See bug 1251045 comment 12.  
> 
> The passing of null goes all the way back to 643325, which is when the
> window argument was added.
> 
> The comment claiming null can't be passed goes back to bug 1092102.  So I
> think the comment is more likely to be wrong.

That comment is from before I started working on this code, so I have no idea if it's supposed to be true or not. Our best bet is probably to ask Kyle here.
Flags: needinfo?(ejpbruel) → needinfo?(khuey)
Er... you added the comment in bug 1092102, no?
(In reply to Boris Zbarsky [:bz] from comment #2)
> Er... you added the comment in bug 1092102, no?

If memory serves, I only renamed Suspend/Resume to Freeze/Thaw in that bug. I changed the comment to reflect those new names, but I did not write the original. See the patch at: https://bug1092102.bmoattachments.org/attachment.cgi?id=8581798
Whiteboard: btpp-followup-2016-03-04 → btpp-followup-2016-03-11
The comment is probably wrong, and might just predate SharedWorkers entirely.
Flags: needinfo?(khuey)
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.