-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
A segmentation fault occurs when using USB connected. #1684
Comments
How long between the start of scrcpy and the disconnection and segfault? Does it happen always? Does it also happen on v1.14 or v1.15? |
Does the segfault appear in |
|
No, when I open another CMD window, and then 'adb logcat', the segfault doesn't appear when connecting to phone. |
It never work once and happen always. I never used other version of scrcpy. |
me too ,system update ,and happen |
@zhaoboy9692 oh so it's also happening on v1.14, also on macOS 😕
Oh, great. Will be easier to find the cause then 😉 @zhaoboy9692 or @Cloudinsea Download scrcpy-server-v1.16, then: git clone https://github.com/Genymobile/scrcpy
cd scrcpy
# edit /path/to/scrcpy-server to point to the server you just downloaded
meson x -Dprebuilt_server=/path/to/scrcpy-server -Db_sanitize=address
ninja -Cx
./run x |
oh no ,dont work |
Thanks 👍
OK, so the segfault does not come from scrcpy itself (nothing is reported by ASAN, and a debug log is printed after the segfault). So either it comes from the device, or from Could you also try with v1.13, please? (v1.14 introduced a fix for #994 which could impact Meizu-specific workarounds #365 #434). |
解决了吗?我也是同样的问题 |
Does |
|
@Dwhy this is not a segfault. https://github.com/Genymobile/scrcpy/blob/master/FAQ.md#exception |
i am sorry,I thought the error of the two mobile phones was the same, so I posted the other one。This is the same as his
|
It's definitely not a segfault in scrcpy, but either on the device or adb. Could you try with older versions of scrcpy? (they also include different version of adb) |
Environment
terminal code:
The text was updated successfully, but these errors were encountered: