Skip to content
This repository has been archived by the owner on Oct 2, 2021. It is now read-only.

Support callstack paging #30

Closed
roblourens opened this issue Jun 8, 2016 · 3 comments
Closed

Support callstack paging #30

roblourens opened this issue Jun 8, 2016 · 3 comments

Comments

@roblourens
Copy link
Member

roblourens commented Jun 8, 2016

P2, 1 day?
Currently we only show 20 frames but now the framework supports this

@roblourens
Copy link
Member Author

I don't think we can actually do this with CDP, since we get all the frames at once in the Debugger.paused event. I don't know that it's a problem though.

@auchenberg
Copy link
Contributor

@roblourens Any reason for why we can't show all frames? Rendering perf?

@roblourens
Copy link
Member Author

Sending info across the wire about lots of frames has bogged down the connection in the past, so we have the option to lazy load them. This might have been more of a problem with the legacy node debug protocol connection, than the connection between the debug adapter and vscode, though.

@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants