Object has been destroyed - Error report for exile-diary 1.0.4
codechaos2017 opened this issue · comments
Error:
TypeError: Object has been destroyed
at EventEmitter.<anonymous> (C:\Users\WILL\AppData\Local\Programs\Exile Diary Reborn\resources\app.asar\build\main\index.js:434:25)
at EventEmitter.emit (node:events:513:28)
at Tail.<anonymous> (C:\Users\WILL\AppData\Local\Programs\Exile Diary Reborn\resources\app.asar\build\main\modules\ClientTxtWatcher.js:126:37)
at Tail.emit (node:events:513:28)
at C:\Users\WILL\AppData\Local\Programs\Exile Diary Reborn\resources\app.asar\node_modules\nodejs-tail\nodejs-tail.js:56:20
at Array.forEach (<anonymous>)
at C:\Users\WILL\AppData\Local\Programs\Exile Diary Reborn\resources\app.asar\node_modules\nodejs-tail\nodejs-tail.js:54:43
at FSReqCallback.wrapper [as oncomplete] (node:fs:675:5)
OS: Windows NT 10.0.22621
App: exile-diary 1.0.4
I closed the other issues, let me know if this is still happening in 1.1.0
First of all thank you for keeping this project alive, while not the OP I am receiving this error when refreshing login.
Of course, my pleasure :)
Interesting... You are seeing this error on 1.1.0 right? If you kill and restart the app, can you accurately trigger this error again?
Yes, I've terminated, reinstalled, and rubbed the launcher icon on Kuduku, but I receive the same error when I refresh the login.
Client version 1.1.0
Interesting, I will try to hit that error on my side then. It should be easy then.
Did you kill all the processes of Exile Diary when you restarted/reinstalled?
Owner
Just got in, I think I might've misunderstood the timing with which to force quit (blame how late it was).
I followed the process of: Launch > Refresh > Force Quit > Authorize > Client Relaunches
This did not yield the error.
Haha all good, I do most of my work on this either at 11PM or 7AM, I have weird moments too.
So, force quitting fixed it then ?
Haha all good, I do most of my work on this either at 11PM or 7AM, I have weird moments too.
So, force quitting fixed it then ?
Sorry for the delay, yes, force quitting before selecting authorize in the browser solved the issue.
For me at least.
I will go ahead and close this one for now, I'm trying to consolidate all the "Object is Destroyed" error altogether. Let me know if it ever happens again!