-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Unable to start on some Linux desktop distributions #9347
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
Comments
应该和 Electron 版本有关系,关联 #9342 |
This comment was marked as outdated.
This comment was marked as outdated.
最后定位到是 main.js 中电源处理代码的问题,Linux 端升级 Electron 26 以后电源相关事件必须放在 whenReady 里面,否则会导致 Trace/breakpoint trap (core dumped) |
仍然有问题:现在能启动了,闪屏结束后进入上一次的笔记的编辑界面,5秒以后白屏,终端输出如下:
|
@ProgramFan 你那里使用了插件吗? |
有插件 |
请帮忙测试一下在没有插件的新工作空间能否重现问题。 |
|
一样的情况,也是闪屏过后2秒就白屏了 |
测试了全新工作空间,删除原工作空间等情形,结果和上面都一样,时间长度不一样。 |
我这里用 Ubuntu 22 虚拟机测试正常,感觉可能是这个问题 electron/electron#32760 |
我在 Wayland 和 X11 两种情况下测试,结果都一样。主要错误在于:
|
ChatGPT 的看法: The error message "Error sending from webFrameMain: Error: Render frame was disposed before WebFrameMain could be accessed" indicates a timing or state issue within an Electron application. Here's a breakdown of what each part means: Error sending from webFrameMain: The error is occurring when trying to send a message from the main process to the renderer process via Electron's WebFrameMain API. Render frame was disposed before WebFrameMain could be accessed: This is the core issue. It suggests that the renderer frame (essentially, a web page within your Electron application) has been closed, navigated away from, or otherwise disposed of before the main process could perform an operation on it via WebFrameMain. The following lines provide a stack trace, indicating where in the code the issue occurred. Here are some common reasons why this could happen: Navigating Away: If the web page in the renderer process is navigated away from or refreshed, the frame would be disposed of. Closing or Reloading the Window: If the Electron BrowserWindow is closed or reloaded, the render frame will be disposed of. Race Condition: Your code might be running asynchronously, and you're trying to perform an operation on the render frame after it's already been disposed of but before your code is aware of that. Debugging Steps Review Asynchronous Code: If you're making asynchronous calls, use appropriate checks or hooks to ensure that the frame still exists when your code runs. Error Handling: Incorporate try-catch blocks or promise-based error handling to catch such exceptions and handle them gracefully. Event Listening: Listen for events like 'closed' on the BrowserWindow object or other events that indicate a change in frame status, and prevent or queue up actions accordingly. Check API Documentation: Ensure that you are using Electron's WebFrameMain and other related APIs correctly. This should give you a good starting point for debugging the issue. |
目前 2.10.7 一切正常,我有办法能测试一下其他版本的 Electron 吗? |
目前 main.js 改动有点多,我们现在再编译一个 dev 版看看。 要测试其他版本只能手动编译打包,scripts/linux-build.sh |
错误依旧,无变化。 |
稍等我们降级一下 Electron 再测测看。 |
新版本工作正常。 |
好的,多谢帮忙测试,晚安了,老铁。
…---Original---
From: ***@***.***>
Date: Mon, Oct 9, 2023 23:42 PM
To: ***@***.***>;
Cc: ***@***.***>;"State ***@***.***>;
Subject: Re: [siyuan-note/siyuan] Unable to start on some Linux desktopdistributions (Issue #9347)
新版本工作正常。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
下个版本我们计划升级到 Electron v27.1.0,可能还会导致这个问题,麻烦看到的老铁帮忙测试。 如果有问题,请到 #9705 中反馈,谢谢。 |
发布可用版本后第一时间测试。 |
27.1.0 正常。 |
terminated by SIGTRAP in Arch
Is there an existing issue for this?
Can the issue be reproduced with the default theme (daylight/midnight)?
Could the issue be due to extensions?
Describe the problem
在 Arch 上使用 2.10.8 的 AppImage 版本会直接退出:
2.10.7 版本是正常的。
Expected result
正常运行
Screenshot or screen recording presentation
No response
Version environment
Log file
No new logs after crashing
More information
No response
The text was updated successfully, but these errors were encountered: