Open thedude61636 opened 4 years ago
Is it always reproducible? Another local stream?
Yes it always happens, first starting a local stream stopping then starting another one This happens if I switch from stream 0 to 1 or from 1 to 0 both will cause the same error I think one solution to this problem is clearing the bitmap before starting a stream
Clearing the currentFrame and writeableBitmap did solve the problem
Using the included demo in this repo selecting a local stream then stopping and selecting another stream causes a System.AccessViolationException in BitmapExtentions.UpdateWith method