# Random SkiaSharp exception

**URL:** <https://community.thinkgeo.com/t/random-skiasharp-exception/12289>\
**Category:** WPF\
**Created:** [December 11, 2025, 8:45am UTC](https://community.thinkgeo.com/t/random-skiasharp-exception/12289 "2025-12-11T08:45:08Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![Ben](https://community.thinkgeo.com/user_avatar/community.thinkgeo.com/ben/32/25720_2.png) [@Ben](https://community.thinkgeo.com/u/Ben)\
**Post date:** [January 12, 2026, 3:55am UTC](https://community.thinkgeo.com/t/random-skiasharp-exception/12289/11 "2026-01-12T03:55:24Z")

</div>

Hi Simo,

We just released v14.4.3, but we didn’t include this change. During testing, we found it could make the peak memory too high. We have an idea to fix both the memory and AccessViolationException, we’ll do it in the beta branch, run more testing, and then bring it into a future stable release once it’s ready. At latest you can have it in v14.5.

Your other request is included in v14.4.3: [OgcApiFeatureLayer and LayerOverlay - ThinkGeo UI for Desktop / WPF - ThinkGeo Discussion Forums](https://community.thinkgeo.com/t/ogcapifeaturelayer-and-layeroverlay/12292)

Thanks,  
Ben

---

_[View the full topic](https://community.thinkgeo.com/t/random-skiasharp-exception/12289)._