Skip to content
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

2.1.0 Prerelease 6 crash #119

Closed
xzhuiz opened this issue Jul 8, 2021 · 11 comments
Closed

2.1.0 Prerelease 6 crash #119

xzhuiz opened this issue Jul 8, 2021 · 11 comments
Assignees
Labels
bug Something isn't working

Comments

@xzhuiz
Copy link

xzhuiz commented Jul 8, 2021

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

@kingToolbox
Copy link
Owner

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!

@kingToolbox kingToolbox self-assigned this Jul 9, 2021
@kingToolbox kingToolbox added the bug Something isn't working label Jul 9, 2021
@kingToolbox
Copy link
Owner

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.

@xzhuiz
Copy link
Author

xzhuiz commented Jul 15, 2021

@kingToolbox WindTerm_2.1.0_Prerelease_7 is better than WindTerm_2.1.0_Prerelease_6
but it's sad, it still crashed
There are two core dumps here, one clicks the window control in the upper right corner, and the other seems to open one tab

e4cfb9af-2e92-43b3-9328-053def776191.zip
59727d5e-c8ee-4920-8ce7-e47022a17061.zip

@kingToolbox
Copy link
Owner

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.

@kingToolbox
Copy link
Owner

@xzhuiz
May I ask if you also use dual monitors? I read @Shellfishgene's comment and found that this crash is related to multiple screens. I didn't notice this before, because I don't have dual screens, so I have not been able to self-test this.

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.

@xzhuiz
Copy link
Author

xzhuiz commented Jul 16, 2021

yes,yes, i use a laptop with two external screens.
Come on

@kingToolbox
Copy link
Owner

I think this problem has finally been fixed, and I have released WindTerm_2.1.0, please download and check it now. Thank you.

@kingToolbox
Copy link
Owner

Hello, does the new WindTerm_2.1.0 still crash?

@kingToolbox
Copy link
Owner

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.

@xzhuiz
Copy link
Author

xzhuiz commented Jul 21, 2021

It's been longer than pre 7, no crash
great

@kingToolbox
Copy link
Owner

Thank you for the good news. Welcome to continue submitting new issues and feature requests. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants