-
Notifications
You must be signed in to change notification settings - Fork 565
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
Random crash when executing ssh
after closing the only tab with Cmd-W
#1959
Comments
I think this is an issue with ios_system. It may also happen when launching a command after closing a window you receive a "segmentation fault". I will try to track this down for 17.3.0. Please let me know if you find anything from your side. It is hard to catch though. PS: Other tools in ios_system also have problems when dealing with control sequences, etc... It would be a good moment to take a deep look at them too. |
From Address Sanitizer logs I have attached in OP, it seems that With the traditional "printf" debug method (l2dy-forks/ios_system@0de9a6e), I found a UAF that came from dereferencing This may or may not be related to the segment fault, but is definitely a bug.
|
PS: |
If I recall, and I have not touched this for some time, yeah we should be using separate threads. But there may be some internal mechanisms though that are not working well or that we are not using properly. I have another hunch that there is something with the descriptors getting mixed in some cases. |
Checklist
Configuration
Custom build of Blink commit df04676, iPadOS 17.3.1
Describe the bug
Note: I'm reporting a crash on my custom build of Blink because I don't have access to TestFlight or official build. Please try to reproduce the crash on official build before investigating.
With the following steps, I can reliably reproduce a crash of the ssh command or the entire app after a few attempts.
Steps to reproduce:
ssh <unreachable_host>
(e.g.ssh ::1
) once.Cmd+W
to close the current tab.ssh <unreachable_host>
several times.Address Sanitizer logs
Report 1 of 2:
Report 2 of 2:
The text was updated successfully, but these errors were encountered: