1538345 - Can not open worker file on Slack

Status: NEW

(DevTools :: Debugger, defect, P3)

Description

[:Harald Kirschner :digitarald]

Attachment: image.png

What were you doing?

1. Log into a Slack and open Debugger (I used https://devtools-html.slack.com/, join via https://devtools-html-slack.herokuapp.com/ )
2. Open blob file from the worker in the source panel (blob:https://devtools-html.slack.com/a73aaba7-6b11-2641-9dc4-12dbea0300c5 in my case)

What happened?

Cryptic error: Error loading this URI: Could not load the source for blob:https://devtools-html.slack.com/a73aaba7-6b11-2641-9dc4-12dbea0300c5. [object Object]

What should have happened?

File is loaded. (Works in Chrome.)

Comment 1

[Logan Smyth [:loganfsmyth]]

Any idea of this is a new issue, or could we just never debug blob-URL workers?

Comment 2

[:Harald Kirschner :digitarald]

Workers from blobs work, can be tested on https://clooney-examples.glitch.me/promises.html

Comment 3

[Jason Laster [:jlast]]

Can we reproduce this without a worker. i.e. do blobs fail on the main thread?

Comment 4

[:Harald Kirschner :digitarald]

Since blobs work in general, moving out of m1.

Comment 6

[Logan Smyth [:loganfsmyth]]

I don't think you'll run into this now unless the script has been GCed and we try to resurrect it, so this should be much better than before.

I think we probably need to have a real conversation around how we decide to restore sources after they've been GCed, which is why I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1645942. I'd love to remove our logic for trying to re-fetch sources if they've been GCed, because it means we still need to try to re-fetch sources in cases like this even if it's not always possible. Better to just accept that things are GCed, and instead focus on not GCing them as aggressively.

Comment 7

[Sherman Davidson]

Attachment: same problem

Thanks from eslafsice1985.