Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
4.5.2f1
Issue ID
625149
Regression
Yes
Calling WebCamTexture.GetPixel(..) after .Play() causes a crash (OSX)
To Reproduce:
1. Open the attached 'repro453p1.zip' & run scene 1.
2. Observe that Unity crashes on the second WebCamTexture.GetPixel(..) line (the one after play).
Regression from 4.3.4f1
Comments (2)
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
Kurt-Dekker
Feb 16, 2015 23:12
This seems to be some kind of race condition: if you wait a second from when you start the WebCamTexture, then read with .GetPixel(), it appears not to crash. That's not very reassuring inasmuch as it still might be stomping on something else, but perhaps it's a datapoint for the fellow in charge of fixing this annoying bug. :)
And keep in mind this is after cross checking .didUpdateThisFrame and .isReadable to make sure things are valid.
Kurt-Dekker
Feb 04, 2015 23:53
We are trying to develop an iOS/Android app and we are not able to test in the editor. I believe it is for this reason. Any attempt at using .GetPixel() on a WebCamTexture results in the editor instantly crashing.
Is there any visibility as to when this might be fixed? Is there any easy workaround? Do we need to render to a render texture and then read the rendertexture pixels instead?