Open 1562791944 opened 3 years ago
Sorry, the instability of WindTerm has caused you trouble. May I ask what operation or condition will cause the crash? Thank you.
Sorry, the instability of WindTerm has caused you trouble. May I ask what operation or condition will cause the crash? Thank you.
os:macOS monterey beta3 pc:MacBook Pro (13-inch, 2019, Four Thunderbolt 3 ports) version:WindTerm 2.1.0
@taolive Thank you for the detailed information.
Can someone tell me how to trigger the crash? For example, which button was clicked, what operation was performed, or it crashed inexplicably, I hope to get a clearer description of the crash to reproduce the failure or analyze it. Otherwise, it is difficult for me to solve the problem because I have tried a lot of operations but still without crashing.
Thank you all.
@taolive Thank you for the detailed information.
Can someone tell me how to trigger the crash? For example, which button was clicked, what operation was performed, or it crashed inexplicably, I hope to get a clearer description of the crash to reproduce the failure or analyze it. Otherwise, it is difficult for me to solve the problem because I have tried a lot of operations but still without crashing.
Thank you all.
Didn't click any buttons or when writing commands or place for a period of time
@taolive Sorry, I am a little confused. If nothing is done, not even caused by idleness, how does the program crash?
@taolive Sorry, I am a little confused. If nothing is done, not even caused by idleness, how does the program crash?
yes, That's it! Where is the dump file? when program crash
Unfortunately, for performance reasons, except for the Windows version, neither the macOS version nor the Linux version has the crash report feature.
I will try to reproduce this bug and repair it. If the plan is not successful, I will integrate the crash report in the next version to fix this problem.
This problem may only be related to macOS version, because there has not been such a report for the Windows version and the Linux version so far.
Unfortunately, for performance reasons, except for the Windows version, neither the macOS version nor the Linux version has the crash report feature.
I will try to reproduce this bug and repair it. If the plan is not successful, I will integrate the crash report in the next version to fix this problem.
This problem may only be related to macOS version, because there has not been such a report for the Windows version and the Linux version so far.
Thank you very much. The error log indicates that an error occurred while allocating memory and caused a crash. But because error log lacks symbols, more conclusions need to be drawn through decompiling WindTerm. This usually takes a lot of time. If the solutions I just mentioned don't work, then I will do it.
Two serious problems (MacBook Air (M1, 2020) )
I think this crash should be related to MacOS only, because there are no crash reports from other systems. The next Mac prerelease version will integrate the breadpad to see if I can find the specific crash location through the crash report.
BTW: When Apple releases the new M1 Macbook Pro in September, I will release the WindTerm M1 version, which should be stable enough by then.
OS: Windows 10 pro HW: Dell Latitude E5250 version:WindTerm 2.1.0 sometimes crashes too. The situation is the same as described above .
Do you mean Windows? WindTerm_2.1.0_Windows_Portable has already integrated the breadpad, and will generate a crash report when WindTerm crashes. The crash report is just in the current working directory after the crash, such as 8f9a5ae5-4ea2-170e-55e9b70e-05c9ab40.dmp
, If you can, you can post it as an attachment in the issue or email me. I will analyze it and fix the problem. Thank you.
The crash report is a standard minidump
file and does not contain any private information. You can read this comment to learn more.
By the way, a known bug that can cause a crash is that after the session is disconnected, someone still try to save and upload files that have been opened by sftp
. This problem will be fixed in subsequent versions.
@cndeng Thank you very much. I have analyzed the crash report. The report shows that there may be an error when highlighting the same instances of the caret word.
However, the minidump format report contains very little debug information, so some tests need to be done to obtain more analysis data. I will continue to investigate this issue and will update it here if there is progress.
+1
ping htop
Sorry for having kept you waiting for so long. I think I have found the problem and fixed it. Currently, the fixed version has not crashed in the past few days of testing. Of course, there may be still other problems that caused the crash, but judging from the performance of the Linux and Windows versions, the stability is still good.
The reason why currently only the MacOS version often crashes lies in the code compilation of the Clang compiler, especially for the voliate
keyword, which is not the same as the GCC compiler (used by the Linux version) and the Visual C++ compiler (used by the Windows version).
I have also been busy developing the SSH MasterControl feature these days. I originally hoped to complete the feature as soon as possible and then release it with this bug fix as WindTerm_2.1.0_Prerelease_1 version. However, the development is more difficult than I expected. More than 10,000 lines of code need to be refactored, so if necessary, maybe I will release a bugfix version first. Please continue to pay attention, thank you.
+1 WindTerm_2.1.0_Mac_Portable sometimes crashes Can you release a bugfix version first? Thank you!
Sorry, WindTerm MacOS version still crashed after being fixed during the self-test, so I am still working hard to fix it completely. Since this is caused by the Clang
compiler and only exists in the release
version, the debug
version is stable, so it is a bit difficult to fix.
I hope to complete the fix as soon as possible.
+1 . macOS big sur 11.5.2 have the same problem .
+1
+1
您的来件我已收到!
Sorry for taking too long to fix this problem.
Yesterday I released a new version WindTerm_2.3.0_Prerelease_2_Mac_Portable_x86_64, and thankfully there have been no reports of new crashes so far. So please download and check the new prerelease version, and thank you all for your patience.
If there are still crashes in use, please use sudo launchctl limit
to check the value of maxfiles
first. If the number is small, then you can use sudo launchctl limit 10240 unlimited
to spcify a much higer number. In this way, WindTerm
should not crash again.
您的来件我已收到!
+1