“Maximum call stack size exceeded” when importing a Logseq folder into a DB graph

[enel1jk]

Search first

• I searched and no similar issues were found

What Happened?

When importing a Logseq folder to a DB graph, I encountered a Maximum call stack size exceeded error. I do have a few relatively large files, with some of them containing around 45,000 lines each.

Reproduce the Bug

1. "import existing notes"
2. "File to DB graph"
3. uncheck "remove inline tags"
4. submit
5. the console first shows several:"Maximum call stack size exceeded", then a large number of "No parent page found for #uuid "6a293234-ce26-447f-80d1-172494e49936""
6. After the import completed, I checked the graph and found that many files were missing.

Expected Behavior

No response

Screenshots

Files

No response

Browser, Desktop or Mobile Platform Information

windows 11 25H2, edge 149.0.4022.52, test.logseq.com 2.0.1

same as chrome 149.0.7827.103 and desktop logseq 2.0.1-alpha+nightly.20260609

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

• I'm willing to submit a PR (Thank you!)

[enel1jk]

I tried launching Logseq from PowerShell using: .\Logseq.exe --js-flags="--stack-size=8192". This resulted in a different issue:

[tiensonqin]

@enel1jk Can you send me the graph to tienson@logseq.com to give it a try?

[enel1jk]

sorry, too much personal information. but if needed, I can provide more logs or other information. i've been stuck at the "import" for about a year now.

[tiensonqin]

@enel1jk No problem, I tried to fix a few issues on import, can you try the latest nightly release?
If it doesn't work, can you search 6a293234-ce26-447f-80d1-172494e49936 in your notes and check whether a page or a block has this id?

[enel1jk]

hi.

I tried the latest nightly release, but the issue still persists.

This time I launched Logseq normally by double-clicking the executable, rather than using the command I mentioned earlier (.\Logseq.exe --js-flags="--stack-size=8192"), but I encountered the same issue.

The import process eventually gets stuck on the progress bar. After closing the progress bar and restarting Logseq, I found that many pages were still missing.

I searched for 6a293234-ce26-447f-80d1-172494e49936 (both in the graph where the import failed and in the normal file-based graph), but no results were found.

Here is the console log:

（The middle section is repetitive, and it ends like this:）

[enel1jk]

any updates?