-
Notifications
You must be signed in to change notification settings - Fork 15.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Invalid PlatformChannel receive right when closing better-sqlite3 database (Possible regression) #39600
Comments
We can probably safely say it's caused by #38826 then. I'll see what i can do. |
This comment was marked as abuse.
This comment was marked as abuse.
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Electron or in the beta—please include it with your comment! |
@ZIMkaRU Hi, seems you have a workaround for this? Does it work? If it worked, I will close this. |
Hi @linonetwo |
Preflight Checklist
Electron Version
26.0.0electron v26.0.0-beta.2What operating system are you using?
macOS
Operating System Version
13.5 (22G74)
What arch are you using?
x64
Last Known Working Electron version
25.6.0electron v26.0.0-beta.1Expected Behavior
No crush or error.
Actual Behavior
Immeadately crush with this output in the console:
Testcase Gist URL
https://gist.github.com/linonetwo/aa3d3ad829a3497af6bc1e269c2a613e
I bysect in fiddle to make sure bug happen between electron v26.0.0-beta.1 ~ v26.0.0-beta.2
Additional Information
Electron fiddle seem to have problem installing better-sqlite3 electron/fiddle#1444
So in the gist I use
nativeBinding: '/Users/linonetwo/Desktop/repo/TiddlyGit-Desktop/node_modules/better-sqlite3/build/Release/better_sqlite3.node'
You may need to install
better-sqlite3
somewhere and get the file path like this, and modify this line, sorry!Otherwise it will error:
The text was updated successfully, but these errors were encountered: