Search Issue Tracker
By Design
Votes
0
Found in
2022.3.60f1
6000.0.43f1
6000.1.0b11
6000.2.0a7
Issue ID
UUM-100175
Regression
No
Crash on __pthread_kill when initializing Vuplex WebView while entering the Play Mode
Reproduction steps:
1. Open the attached “repro_IN-96283“ project
2. Open the “Assets/_ScreeningRoomPro/Scenes/APIFlow.unity“ Scene
3. Enter the Play Mode
4. Observe the crash
Reproducible with: 2022.3.60f1, 6000.0.43f1, 6000.1.0b11, 6000.2.0a7
Reproducible on: macOS Sequoia 15.3 (M2 Ultra), macOS Sequoia 15.4 (M2) (user’s)
Not reproducible on: Windows 10 (22H2), Windows 11 (23H2)
First few lines of the stack trace:
#0 0x000001a0bec704 in __pthread_kill
#1 0xc13a8001a0b31ae8 in abort
#2 0xa0400001a0bdcb84 in __cxxabiv1::__aligned_malloc_with_fallback(unsigned long)
#3 0x6d2e0001a0bcc3d0 in demangling_terminate_handler()
#4 0xa0758001a08a2e58 in _objc_terminate()
#5 0x9a340001a0bdbf48 in std::__terminate(void (_)())_
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
- Multiple errors occur when setting the Render Object Event to AfterRenderingPostProcessing while using STP for Upscaling
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
Resolution Note:
The reason for the crash is corrupted plugin.
Editor log contains this detailed message:
Launch path: "<project_path>/LSVR_ScreeningRoomPro_Quest/Assets/Vuplex/WebView/Standalone/Mac/Plugins/VuplexWebViewMac.bundle/Contents/Frameworks/Vuplex WebView.app/Contents/MacOS/Vuplex WebView"
Exception: "launch path not accessible"
And "Vuplex WebView.app" directory does not exist. Most likely it was a MacOS security that removed it a suspicious, but it is not present in the zip archive provided in this ticket.
I've also found this, which looks official Vuplex info on this issue: https://support.vuplex.com/articles/mac-chromium-failed-to-start