Closed Bug 1555830 Opened 6 years ago Closed 5 years ago

Call stack not always source mapped on first pause

Categories

(DevTools :: Debugger, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: Harald, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Attached image Paused in note.js

What were you doing?

  1. Open Debugger on https://tuner.cloud/
  2. Set BP in the constructor of webpack:///note.js
  3. Refresh to hit BP
  4. Step once

What happened?

On first Pause: Line isn't marked and Call stack is showing unmapped files (app.ff8e2a.js).

Stepping once shows the right Call stack. Sometimes clicking the source maps the call stack as well.

What should have happened?

Works in Chrome, see screenshot.

I could easily reproduce this issue on my main Nightly profile, but not on a fresh profile.

Priority: -- → P3

Are you still able to reproduce this? I just tried a bunch of times but the mapped frames do eventually show up for me after a couple seconds.

Flags: needinfo?(hkirschner)
Attached image image.png

I can see proper callstacks but, I can't set BP on line 3, 4 and 5
Honza

Mentioned offline, but the lack of breakpoints on line 3-5 is because the underlying file is minified, and since we only allow breakpoints at the start of statements, or at function calls, minification that merges many statements into a single comma expression statement will reduce the number of breakable positions, resulting in what we see here. If that's something we wanted to explore somehow, we'd want to file a different bug for it.

Sorry for the delay in replying. WFM when testing again.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(hkirschner)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: