-
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
Crash #110
Comments
Only prerelease 4 version |
Does it crash during startup or during operation? Also, does |
The last stable release was prerelease 2. |
I also found a bug that caused a crash during the development process, but it has not been analyzed yet, and it is not certain that you encountered it. But I will fix it as soon as possible and analyze whether there are other possible crashes. I will update the progress here. Thank you. |
Crashes when switch between tabs... |
Hello, I just released the new WindTerm_2.1.0_Prerelease_5, although the stability is not enhanced, it is still recommended that you download and use it From now on, I will focus on fixing the bugs to make the version stable enough. If you experience a crash again, please let me know, thank you. |
Prerelease 5 crashes/closes when I open a second tab after reconnecting in the first tab:
This works, but crashes on closing WindTerm:
If "reconnect at startup" is off this problem does not appear. |
Two more:
Also:
Actually don't need to take focus from WindTerm:
Note that I use "X mouse" or "focus follows mouse" in Windows 10, not sure if that has anything to do with it. |
One more: WindTerm crashes when I have a terminal tab open and then try to turn off the status bar via View->Bars. If no terminal tab is open it works as expected. |
I upgraded to 5 prerelease, and after "duplicate view" program is crashed |
@SlaviusPrime, what session are you copying, SSH session or shell session? Is there a split window? I just copied it more than a dozen times without any problem. I am still following Shellfishgene‘s steps to reproduce the crash, but so far I have not encountered a crash. But the test is still in progress. The development cycle of this version is too long and there are too many features added, so there are indeed many unstable factors. In the next few days, in addition to compiling the MacOS version of WindTerm, the most important thing is to fix the stability problem, which is why the post is pinned. There is no crash report available now, which makes it difficult to locate the problem. If necessary, I will add the google/breakpad to get a detailed crash report soon. |
Trouble in SSH session without split window. My OS - Windows 10 Pro 19043.1055 |
No, I'm pretty sure about this. When I test the number of tabs, I will open 300 to 500 tabs at the same time, and I will duplicate, close and reopen a large number of tabs. So 15 tabs should be no problem. Although it seems that there are crashes everywhere now. But I estimate that only one or two pieces of code that caused the crash. I am reading the code, but the analysis process is a bit slow. I am also waiting for more crash issues to appear for analysis. |
Today crashed when I try open new ssh session from Sessions tab. |
Do you mean the tooltip of the tab? Add
I have test it and it works. In theory, the preview window will no longer be displayed and will not trigger the bug, but I don't know if it will work in practice. But you can try it. And I am very sorry that this version is not stable yet, which has brought trouble to your use. Almost no crashes were reported in previous versions, I think the instability of this version is likely to be introduced by fixing issue #73 and #78. It's just that I can't reproduce this bug, so I haven't been able to fix it quickly. In order to solve the problem faster, I have been integrating |
I created a new shell session, every time I try to open the shell session, windterm crashed immediately ! 问题签名: and I switched a user, and click the shell session, it works very well. |
@lishuhuakai, your crash may be due to a conflicting version of |
@Shellfishgene, @SlaviusPrime, @gooker. Thank you very much for providing detailed steps to reproduce the crash. I tried each step carefully and repeatedly, including the setting of external conditions, such as "focus follows mouse" mentioned by @Shellfishgene. Unfortunately, the crash has not been reproduced yet. Although I also review the code, as I mentioned above, I am integrating If all goes well, the new WindTerm_Prerelease_6 will be released this weekend together with the MacOS version. |
Also encountered crash few times. No pattern yet. It just disappeared suddenly. Then I had to start it again. |
A new version with If you encounter a crash again, you can submit the generated crash report in the current working directory, such as I have experienced the pain of an application crashing at any time, so I hope to fix the crash and release a stable official version as soon as possible. |
Hi, 05ace889-5e17-4add-bbbd-3a8a4a1211c3.dmp Login screen, click elsewhere, click login screen again, crash (every time) windterm.mp4What actually keeps me from using WindTerm at the moment is also a good menu to set the font and font size ;) Hope it helps! |
Than you very much! |
@kingToolbox what you said cannot solve my problem, here is the dump file. |
@Shellfishgene First of all, thank you for the detailed test. To be honest, although I cannot reproduce any crash myself, I am still surprised that such a simple operation will cause a crash, as if the entire program is riddled with holes. But fortunately, most users used it well, so your crash reports are very important for me to fix it. I understand your concerns. Because
This article Crash Dump Analysis also describes how to use I hope my explanation can eliminate some of your worries. If you can email the dumped files to me, please send them to |
@SlaviusPrime I don't know what you have modified, but I think you can compare and merge yours |
@lishuhuakai Thank you very much. I will analyze the minidump files as soon as possible and give the result here. 😃 |
2.1.0 Prerelease 6 also crashed. |
Yes, the WindTerm_2.1.0_Prerelease_6 version does not fix the crash problem, but adds the feature of collecting crash reports, so that once there is a crash, you can find the crash report in the current working folder, upload it here or email to |
Sended dump to email. |
Crashed with typically scenario. |
And 1 more dump to e-mail. |
@Shellfishgene @SlaviusPrime @xzhuiz I will continue to analyze the code and fix it as soon as possible. I will update here once there is progress. If all goes well, the 2.1.0 version should be released soon. 😄 |
@lishuhuakai
Regardless of success or failure, please let me know so that we can solve the problem further, thank you very much. |
@kingToolbox I remove |
@lishuhuakai |
I removed C:\Users\anyone\AppData\Local\Programs\Microsoft VS Code\bin; |
@SlaviusPrime @lishuhuakai Deleting variables actually does not really solve this problem, but it reduces the probability of crashes. It has been fixed now, and there is no need to delete any environment variables. please download WindTerm_2.1.0_Prerelease_7, thank you all. |
@Shellfishgene @SlaviusPrime @xzhuiz |
Hi,
These only happen when I move WindTerm to my second screen right after I start it! I'm kinda used to have terminal stuff on the right screen so I always move the window right after it appears. So: This one seems to be fixed, no matter the screen:
|
@Shellfishgene When I analyzed the crash reports, I found that this was caused by the screen change event, but I have never understood why the screen change occurred. I used to think it was caused by changing the resolution of the monitor, but usually no one would modify it when using a software. From your description, I realized that I actually ignored dual monitors. Because I only have one monitor, I think this is why I cannot reproduce the crash you mentioned. So I think the remaining thing is that I need to set up a dual-monitor environment for further testing, because it is difficult to solve the problem further from the code review. I will continue to solve this problem. I hope that you can use WindTerm to make your work easier instead of testing WindTerm. Thank you again. |
I'm really happy that I should finally fix this issue and the stable WindTerm_2.1.0 has been released too, please download and check it, thank you. I managed to set up a dual-monitor environment, and when I saw the crash, I knew that I could solve the problem. I have also done a lot of tests, including opening more than ten of windows in the second monitor and disconnecting it to see if all windows can be correctly returned to the main monitor, and so on. Thanks to everyone who has helped. Without you, it would be very difficult for me to even find this problem because I only have one monitor during my daily development. I always hope you only need to use WindTerm instead of testing WindTerm, and make your work easier and more efficient. Now WindTerm can finally move forward, and I'll keep on trying. BTW: |
2.1.0 does not crash for me anymore! |
Thank you for the good news. I am very happy to finally let you use WindTerm normally. It looks like this issue should have been fixed. To disable syntax highlighting for all new connections, you need open I'm a little curious, why do you want to disable it? Does this feature hinder anything? |
Not really, but I have colors in my terminal already, for example I use a version of |
@Shellfishgene In addition, if the syntax highlighting is disabled, features such as folding, outling will also be disabled at the same time, but the advantage is that the overall performance will be a little faster. |
The issue should have been fixed in the new WindTerm_2.1.0. Welcome to continue submitting new issues and feature requests, thank you. |
Program crashes sometimes.
No problem dependency found
The text was updated successfully, but these errors were encountered: