Search Issue Tracker
Fixed in 5.6.0
Votes
2
Found in
5.5.0f1
Issue ID
855603
Regression
Yes
[Android] Crash when reloading scene which uses WebCamTexture
How to reproduce:
1. Open the attached project
2. Build and run on Android device
3. Click on Button (it stops rendering RawImage and loads the same scene again )
4. Crash
Reproducible: 5.5.0b1, 5.5.0f3, 5.6.0a5
Not reproducible: 5.4.3p2
Comments (8)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
smosh92
Sep 10, 2017 07:20
ok it's fixed in Unity 2017.1.0f3
smosh92
Sep 10, 2017 07:04
"webCamTex.Stop()" still crashing on android build!!
UDN_94209c12-b028-4555-8598-0bb083bb0452
Jul 11, 2017 02:43
It seems that you need to stop the webcamtexture inside OnDisable method when unload the scene.
OscarPeredo
Jun 15, 2017 06:31
Definitively not fixed....
aggRo
May 10, 2017 14:07
WebCamTexture.Stop on Android ... still crash
esoinila
May 03, 2017 12:49
Now there is clearly something wrong with the WebCamTexture.Stop on Android ... still it keeps getting marked as fixed but never is. Stop marking these bugs fixed until they are really tested.
sunderplugs11
Feb 20, 2017 04:14
also, mine is crashing just minimizing the app and going bakc into it. I'm calling WebCamText.Stop() on each of the 3 textures i'm using in the OnAppPause() function
sunderplugs11
Feb 20, 2017 04:12
so I downloaded the beta of 5.6 and its still crashing? Need to publish asap so any idea on workaround till then?