Exception Object has been destroyed
See original GitHub issueUncaught Exception:
Error: Object has been destroyed
at Error (native)
at exports.default.appWindow (/Applications/Cerebro.app/Contents/Resources/app.asar/webpack:/app/main/createWindow/toggleWindow.js:6:17)
at Function.toggleMainWindow (/Applications/Cerebro.app/Contents/Resources/app.asar/webpack:/app/main/createWindow.js:34:34)
Issue Analytics
- State:
- Created 7 years ago
- Comments:6
Top Results From Across the Web
Object has been destroyed when open secondary/child ...
Uncaught Exception: Error: Object has been destroyed at Error (native) at EventEmitter. (/home/xxxx/electron/fin/main.js:36:21) at emitOne ...
Read more >Object has been destroyed · Issue #1 - GitHub
I found that mainBindings() is creating listeners and not clearing them properly. This is why we get the object destroyed error, the listener...
Read more >The object of type '' has been destroyed but you are still trying ...
MissingReferenceException : The object of type 'DontDestroyOnLoad' has been destroyed but you are still trying to access it.
Read more >Object has been destroyed - General - Navigraph
... I ran into an “uncaught exception:type error: Object has been … ... Object has been destroyed” which seems to be a Java...
Read more >Error: Object has been destroyed | Pinnacle 21
Hello Parth,. Thank you for reporting this issue. Does it happen right when you start the app, when you open Validator, or when...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@KELiON @maximbaz these guys here https://github.com/tinytacoteam/zazu are using a different approach and their app’s search bar doesn’t have this issue, it is getting closed only by pressing
Esc
or clicking outside the window. In their casealt + f4
is closing the app itself (not only the search bar), I think that’s how it should be for Cerebro, this approach will resolve the problem with referencing a destroyed object and raising this exception. What do you think of that guys?@KELiON it’s easy:
Still happens on 0.2.6