1304682 - Worker is no longer shown in debugger

Status: RESOLVED WORKSFORME

(DevTools :: Debugger, defect, P3)

Description

[Jukka Jylänki]

Attachment: cc_crashes.zip

STR:

1. Enable "Enable worker debugging (in development)" debugging checkbox.
2. Open cc_crashes.html just by dragging to browser window, i.e. via file://
3. Open Debugger panel.

Observed:

In Firefox Stable 48.0, there is a Workers panel with cc_crashes.js listed in it.

In Firefox Nightly 52.0a1 (2016-09-21) (64-bit), the cc_crashes.js file is not listed at all in debugger files (and so it can't be debugged).

Comment 1

[Hsin-Yi Tsai (she/her) [:hsinyi]]

I cannot reproduce this; cc_crashes.js is listed.

Comment 2

[Jukka Jylänki]

Attachment: Screen Shot 2016-09-23 at 3.08.38 PM.png

Here is how it looks for me on current Nightly 64bit on OS X. I expect that a worker with cc_crashes.js would show up in the same tree view as cc_crashes.html.

I am running a fresh Firefox profile with only the "Enable worker debugging (in development)" checkbox ticked in "Toolbox Options" panel (under the gearbox icon)

Comment 3

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Moving to the right component, and seeing if someone could manage to reproduce this.

Comment 4

[Eddy Bruel [:ejpbruel]]

Without any background knowledge on how this worker is used: could this be an issue where the worker happens to be GC'd before it shows up in the debugger?

Assigning P3 to this until we can confirm it is a bug.

Comment 5

[Jukka Jylänki]

Attachment: ff_nightly_no_sources.jpg

The worker is not garbage collected, it is persistent and available as globally from console via "Fetch.worker". It is created on line 6226 in cc_crashes.js.

Retested this on another Windows computer in current Firefox Nightly, and the issue reproduces there as well. Attached a screenshot.

Comment 6

[Jukka Jylänki]

Attachment: debugger_hung.jpg

The debugger console is somehow hung after step 3, attempting to type even "5 + 2" does not produce a result.

Comment 7

[Jukka Jylänki]

The issue doesn't seem to be specific to showing a worker script, since the page should probably show the main script "cc_crashes.js" as well, which is loaded in the main browser thread.

Comment 8

[Jason Laster [:jlast]]

I believe this was fixed. Honza, could you verify?

Comment 9

[Jan Honza Odvarko [:Honza] (always need-info? me)]

I can't reproduce this, I can see cc_crashes.js file in the list.

Closing.

@Jukka: feel free to reopen if you are still able to reproduce the problem.

Honza