Uncaught Exception: RangeError: Maximum call stack size exceeded
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 39k
- Forks
- 2.1k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Platform
Desktop - Windows
Describe the bug
I'm not sure if this is a BUG and I can't reproduce it either. This BUG seems to be triggered from time to time, and this is what it prompts
[Window Title]
Error
[Main Instruction]
A JavaScript error occurred in the main process
[Content]
Uncaught Exception:
RangeError: Maximum call stack size exceeded
at console.value (node:internal/console/constructor:302:13)
at console.debug (node:internal/console/constructor:398:26)
at Object.debug (file:///C:/Users/KDCJT/AppData/Local/Folo/app-0.7.0/resources/app.asar/dist/main/index.js:76183:17)
at #waitForData (file:///C:/Users/KDCJT/AppData/Local/Folo/app-0.7.0/resources/app.asar/dist/main/index.js:81500:24)
at #handleGotMessageSize (file:///C:/Users/KDCJT/AppData/Local/Folo/app-0.7.0/resources/app.asar/dist/main/index.js:81575:26)
at #waitForData (file:///C:/Users/KDCJT/AppData/Local/Folo/app-0.7.0/resources/app.asar/dist/main/index.js:81536:37)
at #handleGotMessageSize (file:///C:/Users/KDCJT/AppData/Local/Folo/app-0.7.0/resources/app.asar/dist/main/index.js:81575:26)
at #waitForData (file:///C:/Users/KDCJT/AppData/Local/Folo/app-0.7.0/resources/app.asar/dist/main/index.js:81536:37)
at #handleGotMessageSize (file:///C:/Users/KDCJT/AppData/Local/Folo/app-0.7.0/resources/app.asar/dist/main/index.js:81575:26)
at #waitForData (file:///C:/Users/KDCJT/AppData/Local/Folo/app-0.7.0/resources/app.asar/dist/main/index.js:81536:37)
[确定]
By the way, when I tried to click the "Export Database" button before clearing the data and reinstalling it, there was no response. When I click the upgrade button, it tells me that I cannot upgrade, so I will put the log file below
Entry ID
No response
Relevant Information
No response
Reproduction Video
No response
Environment
Environment
App Version: 0.7.0
OS: Windows
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Folo/0.7.0 Chrome/138.0.7204.97 Electron/37.2.0 Safari/537.36
Env: electron
Browser: Chrome
Session Trace Id: HmUAZiwzK4yOe7qZfFvS9
Mode: production
Renderer: 0.7.0
Validations
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
- This issue is valid
Contributions
- I am willing to submit a PR to fix this issue
- I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached main.log and the stack trace in dist/main/index.js for app version 0.7.0. Trace the interaction between #waitForData and #handleGotMessageSize, then establish a reproducible case and verify that the main process no longer reaches the maximum call stack while database export and upgrade actions remain usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100