Unity-Technologies / Unity-Technologies/com.unity.webrtc
[BUG] WebRTC unity interfere's with native CUDA plugins
Nobody has claimed this yet.
- Dominant language
- Assembly
- Stars
- 852
- Forks
- 238
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I have an existing plugin that executes CUDA kernels on a separate thread. When the WebRTC plugin is installed in Unity, the existing CUDA library which worked perfectly fine (on the separate thread), starts to cause Illegal memory access issues. This happens every-time we issue any device read calls from another thread. This seems to work fine if all CUDA memory accesses are done on Unity's UI thread.
Any idea what may be happening behind the scenes? Note that I do not even use the library yet. I simply install the plugin.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names the Unity WebRTC plugin and a native CUDA plugin but no repository files or tests. Start by reproducing device-read calls from the CUDA plugin's separate thread with WebRTC installed, then inspect the plugin's native integration and threading assumptions. Done means the interaction is explained and a reproducible fix or documented limitation is established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- unity
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100