Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

debug - large ArrayBuffer kills debugging #5811

Closed
jrieken opened this issue Apr 26, 2016 · 2 comments
Closed

debug - large ArrayBuffer kills debugging #5811

jrieken opened this issue Apr 26, 2016 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues important Issue identified as high-priority verified Verification succeeded

Comments

@jrieken
Copy link
Member

jrieken commented Apr 26, 2016

#4951

  • take default extension from yo code
  • put this inside the command
        let v = process.version;
        console.log(v);

        let buffer = new ArrayBuffer(320000);
        console.log('byte buffer', buffer.byteLength);

        let view = new Int32Array(buffer);
        console.log('int32 view', view.length);

        for (let i = 0; i < view.length; i++) {
            view[i] = i * 2;
        }

        console.log('made it...');
  • put a breakpoint on the first and last line
  • run, break, steps until the for-loop, hint continue to run the last statement
  • ⚡ eventually I get told that nodejs isn't responding anymore, debugging is in a weird state like Continue, Stepping being enabled but dysfunctional
@jrieken jrieken added bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority debug Debug viewlet, configurations, breakpoints, adapter issues labels Apr 26, 2016
@bpasero
Copy link
Member

bpasero commented Apr 26, 2016

@jrieken assigning back to you to retest this scenario with a newer Alpha build that includes our node-debug fix to actually enable debug injection for Electron.

@jrieken
Copy link
Member Author

jrieken commented Apr 26, 2016

fixed with latest changes

@joaomoreno joaomoreno added the verified Verification succeeded label Oct 28, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants