microsoft / microsoft/AzureStorageExplorer
Crash on exit
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 452
- Forks
- 92
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Description
Storage Explorer Version: v1.2.0
Platform/OS Version: Windows 10 Pro v1709 build 16299.492
Steps to Reproduce:
- Unknown
Expected Experience:
App quits
Actual Experience:
App throws an exception on quit (contents of dialog box below)
A JavaScript error occurred in the main process
Uncaught Exception
Error: Object has been destroyed
at WebContents.send (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\electron.asar\browser\api\web-contents.js:100:15)
at C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\se-electron-file-downloader\dist\ElectronFileDo....:34
at DownloadItem.<anonymous> (C:\Program Files (x86)\Microsoft Azure Storage Explorer\resources\app\node_modules\se-electron-file-downloader\dist\ElectronFileDo...:17)
at Object.onceWrapper (events.js:317:30)
at emitTwo (events.js:126:13)
at DownloadItem.emit (events.js:214:7)
Bonus Suggestion
There may be errors in the stack trace above. You might want to consider either adding a "Copy Text" button to this dialog or make the text displayed is selectable/copyable if you want more people to bother sending you these details. Typing it out is not ideal.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking whether the crash still occurs in the current application, since the report targets Storage Explorer v1.2.0 and gives no reproducible steps. Inspect the download callback in se-electron-file-downloader, especially the WebContents.send path shown in the stack trace. Done means quitting the app after a download no longer produces an uncaught "Object has been destroyed" exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript, node.js
- Domain
- desktop-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100