-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
2.1.0 Prerelease 6 crash #119
Comments
Wow, my preliminary analysis shows that there is indeed a null pointer access. I think this is at least one of the causes of instability. I will fix it, thank you very much! |
Hi, WindTerm_2.1.0_Prerelease_7 has finally been released and this issue should have been fixed. You can download and check it now. Thank you. |
@kingToolbox WindTerm_2.1.0_Prerelease_7 is better than WindTerm_2.1.0_Prerelease_6 e4cfb9af-2e92-43b3-9328-053def776191.zip |
Yes, unfortunately, the new analysis result still points to the previous error, and a null style pointer is used when drawing the text. It really makes me very frustrated. 😞 I will continue to analyze and try to fix it again. Thank you very much. |
@xzhuiz Maybe this is why I have been unable to reproduce the crash? Because the operation that caused the crash you mentioned is very simple, logically I should be able to reproduce it. |
yes,yes, i use a laptop with two external screens. |
I think this problem has finally been fixed, and I have released WindTerm_2.1.0, please download and check it now. Thank you. |
Hello, does the new WindTerm_2.1.0 still crash? |
The issue should have been fixed in the new WindTerm_2.1.0 and self-test passed. Please reopen this issue if it is still valid. Thank you. |
It's been longer than pre 7, no crash |
Thank you for the good news. Welcome to continue submitting new issues and feature requests. 😄 |
I have been using 2.1.0 Prerelease 3, which is super stable.
Last time I used 2.1.0 Prerelease 5, it crashed
This time 2.1.0 Prerelease 6 also crashed.
There is not much operation, just open a few tabs
core dump as follow
70cbf851-f3b8-469e-81f1-1a30dcd3d52c.zip
The text was updated successfully, but these errors were encountered: