1.3.3 Android version will crash after exiting the application while Re-establishing a new connection. historical versions Don OT have this problem.
Closed this issue · 10 comments
Bug Description
1.3.3 Android version will crash after exiting the application while Re-establishing a new connection. historical versions Don OT have this problem.
How to Reproduce
1，Connect from Windows using the latest version
2，Android crashes when exiting establishing new connection
Expected Behavior
Version 1.3.2 is normal
Operating system(s) on local (controlling) side and remote (controlled) side
Windows10->1.3.3
RustDesk Version(s) on local (controlling) side and remote (controlled) side
1.3.3->1.3.3
Screenshots
e079a44c4b18a4aec0f1d354ad81a11f.mp4
Additional Context
No response
Why can you accept connection with out starting service after exit and open RustDesk again? I even do not know how to do this.
crash log?
I see you are modifying RustDesk, since you can reproduce it and you can debug, I believe you can fix it.
崩溃日志？
Process: com.carriez.flutter_hbb
PID: 21729
Flags: 0x30c8be44
Package: com.carriez.flutter_hbb v1052 (1.3.3)
Foreground: Yes
Build: alps/full_rlk6580_we_c_m/rlk6580_we_c_m:9/PPR1.180610.011/665:user/release-keys
Build fingerprint: 'alps/full_rlk6580_we_c_m/rlk6580_we_c_m:9/PPR1.180610.011/665:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 21729, tid: 22838, name: Thread-22 >>> com.carriez.flutter_hbb <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'indirect_reference_table.cc:59] JNI ERROR (app bug): accessed deleted Global 0x262a'
r0 00000000 r1 00005936 r2 00000006 r3 00000008
r4 000054e1 r5 00005936 r6 c497f424 r7 0000010c
r8 00000000 r9 0000005b r10 ec0fb36c r11 ec0fce94
ip c497f3c0 sp c497f410 lr ed629e59 pc ed621ca6
backtrace:
#00 pc 0001cca6 /system/lib/libc.so (abort+58)
#1 pc 0034db4f /system/lib/libart.so (art::Runtime::Abort(char const*)+910)
#2 pc 000071b3 /system/lib/libbase.so (android::base::LogMessage::~LogMessage()+494)
#3 pc 001b69d5 /system/lib/libart.so (art::IndirectReferenceTable::AbortIfNoCheckJNI(std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator> const&)+172)
#04 pc 0023754f /system/lib/libart.so (art::IndirectReferenceTable::GetChecked(void*) const+270)
#05 pc 002338eb /system/lib/libart.so (art::JavaVMExt::DecodeGlobal(void*)+10)
#6 pc 00373385 /system/lib/libart.so (art::Thread::DecodeJObject(_jobject*) const+168)
#7 pc 002689bf /system/lib/libart.so (art::JNI::GetObjectClass(_JNIEnv*, _jobject*)+402)
#08 pc 005c9777 /data/app/com.carriez.flutter_hbb-oQxdT_dV61Ksdxm8s_GxuQ==/lib/arm/librustdesk.so (offset 0x3f6000)
#9 pc 0007cefc /system/lib/libc.so (ifree+916)
#10 pc 00227be2 /data/app/com.carriez.flutter_hbb-oQxdT_dV61Ksdxm8s_GxuQ==/lib/arm/librustdesk.so
this is the log. ill try to see if i can fix IT. im ammateur and have limited abilities.
arm32?
arm32？
So does aarch64
Why can you accept connection with out starting service after exit and open RustDesk again? I even do not know how to do this.
How can you achieve this?
Why can you accept connection with out starting service after exit and open RustDesk again? I even do not know how to do this.
How can you achieve this?
Isn’t this what the app itself is like? Quit the app and reopen it, the service is still started and not disconnected. After manually clicking to stop the service, the connection will be disconnected.
The fix is marged, please try it out.