This repository was archived by the owner on Mar 3, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 17.3k
This repository was archived by the owner on Mar 3, 2023. It is now read-only.
Unable to save a CPU Profile #13767
Copy link
Copy link
Closed
Labels
Description
Prerequisites
- Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
- Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
- Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
- Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
- Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
A security error is produced when attempting to collect a CPU Profile through the developer tools in Atom.
Steps to Reproduce
- Launch Atom in your local atom repository
- Press Alt+Cmd+I to open the Developer Tools
- Click the Profiles tab in the Developer Tools
- Ensure "Record JavaScript CPU Profile" is selected
- Click Start
- Do a couple random things in the editor
- Click Stop
- Observe that a SecurityError regarding temporary storage is displayed
- Click the Save link next to the new profile record
- Save to
~/Downloads - Get info on the new
*.cpuprofilefile
Expected behavior: The cpuprofile file to be longer than zero bytes
Actual behavior: The cpuprofile file is always zero bytes
Versions
Atom : 1.15.0-dev-ae9d949ee
Electron: 1.3.13
Chrome : 52.0.2743.82
Node : 6.5.0
I also reproduced this using v1.13.1 and v1.14.0-beta4.
Additional Information
Reactions are currently unavailable
