Open Bug 1759573 Opened 2 years ago Updated 2 years ago

Some spurious wasm:// source appear when opening the debugger on a page with asm.js

Categories

(DevTools :: Debugger, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: ochameau, Unassigned)

References

Details

The test added in bug 1757937 highlights that the debugger shows a spurious source.
This source has a wasm:// URL and is sorted independently in the SourceTree.
This only happens when opening the page on an already loaded page and when this page has an ASM.js source.
When we try opening this source, we can't fetch its content and CodeMirror shows an error instead.

The issue boils down to ThreadActor.addAllSources, which calls DebuggerAPI.findSources:
https://searchfox.org/mozilla-central/rev/b0779bcc485dc1c04334dfb9ea024cbfff7b961a/devtools/server/actors/thread.js#1458
And findSources should probably not return this buggy WASM source, whereas it returns a correct entry for the ASM.js source.

The severity field is not set for this bug.
:bomsy, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(hmanilla)
Severity: -- → S3
Flags: needinfo?(hmanilla)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.