Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.32f1
2022.3.14f1
2023.2.1f1
2023.3.0a15
Issue ID
UUM-56826
Regression
No
Crash on MovellaDotPcSdk.movelladot_pc_sdkPINVOKE:XsPortInfoArrayImpl_size (System.Runtime.InteropServices.HandleRef) when closing the Editor during a Bluetooth scan
Reproduction steps:
1. Open the attached “repro-project“
2. Open the “Assets/Scenes/SampleScene.unity“ scene
3. Enter Play Mode
4. Close the Editor
5. Observe the crash
Reproducible with: 2021.3.32f1, 2022.3.14f1, 2023.2.1f1, 2023.3.0a15
Reproduced on: Windows 10
Not reproducible on: No other environment tested
Notes:
1. When entering Play Mode, the application begins scanning for Bluetooth devices, which involves activating several threads
2. As a workaround, you can abort all active Bluetooth-related threads before shutting down these activities
First few lines of the stack trace:
0x0000022A2FA34E09 (Mono JIT Code) (wrapper managed-to-native) MovellaDotPcSdk.movelladot_pc_sdkPINVOKE:XsPortInfoArrayImpl_size (System.Runtime.InteropServices.HandleRef)
0x0000022A2FA34C53 (Mono JIT Code) MovellaDotPcSdk.XsPortInfoArrayImpl:size ()
0x0000022A2F9C73CB (Mono JIT Code) Movella.XdpcHandler:scanForDots (System.Action)
0x0000022A2F9C6CEB (Mono JIT Code) SensorsRecordingScript:<Awake>b__16_0 ()
0x00000229A0D9F372 (Mono JIT Code) System.Threading.ThreadHelper:ThreadStart_Context (object)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Customer found and resolved the issues by aborting the thread before closing the activity.