OneFolderApp / OneFolder

File explorer made for pictures

Home Page:https://onefolder.app

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Encountering "Something went wrong" screen on exit after tag export

just-a-garlic-bread opened this issue · comments

Which actions did you perform before the error occurred?
Bug happened multiple times, when i decided to export the tags to the file's metadata.
To note, he error message doesnt appear immediately, but does so only when i close the settings window.
It doesnt appear when i open and close the settings window without exporting tags.
(Might try to re-download the application, to see if error still persists)

What did you expect to happen?
Usually, when tag saving works out well, the times when it did happen, it showed a saving progress in percentages, instead of immediately saying that it is done(Probably related to it, but im not sure.)

Stacktrace

IPC method called after context was released
    at EventEmitter.send (node:electron/js2c/renderer_init:2:14057)
    at node:electron/js2c/renderer_init:2:32075
    at cleanup (webpack://onefolder/src/frontend/components/PopupWindow.tsx:50:21)
    at safelyCallDestroy (webpack://onefolder/node_modules/react-dom/cjs/react-dom.development.js:22932:0)
    at commitHookEffectListUnmount (webpack://onefolder/node_modules/react-dom/cjs/react-dom.development.js:23100:0)
    at commitPassiveUnmountInsideDeletedTreeOnFiber (webpack://onefolder/node_modules/react-dom/cjs/react-dom.development.js:25101:0)
    at commitPassiveUnmountEffectsInsideOfDeletedTree_begin (webpack://onefolder/node_modules/react-dom/cjs/react-dom.development.js:25048:0)
    at commitPassiveUnmountEffects_begin (webpack://onefolder/node_modules/react-dom/cjs/react-dom.development.js:24956:0)
    at commitPassiveUnmountEffects (webpack://onefolder/node_modules/react-dom/cjs/react-dom.development.js:24941:0)
    at flushPassiveEffectsImpl (webpack://onefolder/node_modules/react-dom/cjs/react-dom.development.js:27038:0)

Runtime info

  • OneFolder version: v0.1.5
  • Operating system: Windows_NT 10.0.19044, win32 x64
  • Node version: v18.17.1

Reinstalling the application helped.Im really sorry for making a rushed decision, it was a mistake on my end