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

Unable to save CPU profiles as files #13704

Closed
miladghiravani opened this issue Oct 13, 2016 · 3 comments
Closed

Unable to save CPU profiles as files #13704

miladghiravani opened this issue Oct 13, 2016 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded
Milestone

Comments

@miladghiravani
Copy link

  • VSCode Version: 1.6.1
  • OS Version: Windows 8.1 Enterprise 64-bit

Steps to Reproduce:
New VS Code now is update but I have problem to save CPU profile on version 1.6.0 and 1.6.1.
When I Start CPU profile and stop, profile is created but when I save this, see zero (empty) size file saved!
I have only 1 extension (beautify).
ashampoo_snap_2016 10 14_00h53m44s_007_

@isidorn
Copy link
Contributor

isidorn commented Oct 14, 2016

This is a chrome bug which should hopefully get fixed soon and which we would get with an electron update in the future.
@bpasero can provide more details if needed

@isidorn isidorn closed this as completed Oct 14, 2016
@isidorn isidorn added upstream Issue identified as 'upstream' component related (exists outside of VS Code) electron-update labels Oct 14, 2016
@bpasero
Copy link
Member

bpasero commented Oct 14, 2016

Yup, got fixed in newer electron releases. We can keep this open to track the issue.

@bpasero bpasero reopened this Oct 14, 2016
@bpasero bpasero added this to the Backlog milestone Oct 14, 2016
@bpasero bpasero self-assigned this Oct 14, 2016
@bpasero bpasero changed the title Problem save CPU profile in vs code 1.6.1 Unable to save CPU profiles as files Oct 14, 2016
@bpasero bpasero added the bug Issue identified by VS Code Team member as probable bug label Oct 14, 2016
@joaomoreno
Copy link
Member

electron/electron#7403

@bpasero bpasero mentioned this issue Nov 10, 2016
11 tasks
@bpasero bpasero modified the milestones: November 2016, Backlog Nov 14, 2016
@bpasero bpasero closed this as completed Nov 14, 2016
@jrieken jrieken added the verified Verification succeeded label Dec 8, 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 upstream Issue identified as 'upstream' component related (exists outside of VS Code) verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants