ThinkGeo.comĀ Ā Ā Ā |Ā Ā Ā Ā  DocumentationĀ Ā Ā Ā |Ā Ā Ā Ā  Premium Support

Random SkiaSharp exception

#21

Hi,

I think that this time it happened actually in place (when ZoomToAsync was called by our app) where we could catch it. But this was the first time this happened in this place so we did not have catch for it so app crashed.

Br, Simo

#22

Hi Simo,

  1. This is a related but different issue. It occurs intermittently due to a race condition.
  2. We have identified and fixed it in the latest beta. The fix will also be included in the upcoming v14.4.5 hotfix.
  3. In the latest beta and the upcoming v14.5 release, AdornmentOverlay has been significantly improved. For a quick preview, please see: Recommended way of having static elements on pannable background

Thanks,
Ben

1 Like
#23

Hi,

This kind of random SkiaSharp related crash was also seen on test automation:

Exception Info: System.AccessViolationException
at SkiaSharp.SKBitmap.CopyTo(SkiaSharp.SKBitmap, SkiaSharp.SKColorType)
at SkiaSharp.SKBitmap.Copy(SkiaSharp.SKColorType)
at Y0c=.EEc=.EUc=(ThinkGeo.Core.GeoImage)
at ThinkGeo.UI.Wpf.TileView.8UY=(ThinkGeo.Core.GeoCanvas)
at ThinkGeo.UI.Wpf.TileOverlay+d__109.MoveNext()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Runtime.CompilerServices.AsyncMethodBuilderCore+MoveNextRunner.Run()
at System.Threading.ThreadPoolWorkQueue.Dispatch()

Please check this also.

Br, Simo

#24

We didnā€™t aware SKBitmap.CopyTo was not thread-safe. Let us dig in and will keep you posted.

#25

Hi,

Any updates to this latest SKBitmap.CopyTo exception ?

Br, Simo

#26

Hi Simo,

We are pretty much done and now reviewing the changes. The new version will once and for all fix it without any performance penalty. It will be available in beta builds next week, and it will be available in the next major release.

We still havenā€™t decided it yet but given the changes weā€™ve made, most likely we cannot put it into a hotfix release. Iā€™ll let you know by mid next week.

Thanks,
Ben

1 Like
#27

Hi Simo,

I donā€™t think we can include this change in the hotfix release next week, it will for sure be included in the major release in May.

Thanks,
Ben

#28

Hi Simo, just FYI the fix has been applied to beta package(beta099).

#29

Hi,

Thanks for the info.

Br, Simo

#30

Hi Simo, just FYI v14.4.5 is now available.

1 Like