You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was creating new tags (and setting the parent tag to the current page node) and now I can't load Logseq due to the browser returning an out of memory issue. The app is completely unresponsive.
I think I know exactly which tag is causing the issues but also unable to generate logs as I side loaded the tag and now it's stuck always trying to load the tag regardless of the current navigation pane.
Reproduce the Bug
I have a backup from a few hours ago so could try re-produce but if you have any ideas how I could force logseq to close the side pane then I could export the current DB for analysis in case I can't recreate.
I've managed to somehow hide to right side pane which was causing the issue while trying to load a tag (by quickly mashing 'tr' on load of the webpage). On export of the EDN file I'm getting the following error in the console:
export-edn error:
$APP.nh
cause: null
columnNumber: undefined
data: $APP.l {meta: null, ga: 1, Z: Array(2), O: null, V: 16647951, …}
description: undefined
fileName: undefined
lineNumber: undefined
message: "The following classes, uuids and properties are not defined: {:uuids #{#uuid \"00000002-1454-9866-4100-000000000000\"}}"
name: "Error"
number: undefined
stack:
"Error: The following classes, uuids and properties are not defined: {:uuids #{#uuid \"00000002-1454-9866-4100-000000000000\"}}\n at new $APP.nh (https://test.logseq.com/static/js/shared.js:1062:31)\n at $APP.Jj.F (https://test.logseq.com/static/js/shared.js:3079:319)\n at $APP.Jj.C (https://test.logseq.com/static/js/shared.js:3079:273)\n at CSe (https://test.logseq.com/static/js/db-worker.js?electron=false&publishing=false:544:378)\n at LUe (https://test.logseq.com/static/js/db-worker.js?electron=false&publishing=false:696:95)\n at Function.<anonymous> (https://test.logseq.com/static/js/db-worker.js?electron=false&publishing=false:1839:85)\n at jha (https://test.logseq.com/static/js/shared.js:986:386)\n at kha (https://test.logseq.com/static/js/shared.js:986:311)\n at $APP.Re.C (https://test.logseq.com/static/js/shared.js:2654:168)\n at $APP.y4a (https://test.logseq.com/static/js/shared.js:2418:172)"
[[Prototype]]: Error
Ua: {}
na: ƒ (a,b,c)
toString: ƒ ()
constructor: ƒ (a,b,c)
[[Prototype]]:Object
Search first
What Happened?
I was creating new tags (and setting the parent tag to the current page node) and now I can't load Logseq due to the browser returning an out of memory issue. The app is completely unresponsive.
I think I know exactly which tag is causing the issues but also unable to generate logs as I side loaded the tag and now it's stuck always trying to load the tag regardless of the current navigation pane.
Reproduce the Bug
I have a backup from a few hours ago so could try re-produce but if you have any ideas how I could force logseq to close the side pane then I could export the current DB for analysis in case I can't recreate.
Expected Behavior
No response
Files
No response
Browser, Desktop or Mobile Platform Information
logseq/logseq@2d8b343
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: