# Browser Library Error

**URL:** <https://forum.inductiveautomation.com/t/browser-library-error/60198>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [May 31, 2022, 10:28am UTC](https://forum.inductiveautomation.com/t/browser-library-error/60198 "2022-05-31T10:28:23Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![cmallonee](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmallonee/32/6416_2.png) [@cmallonee](https://forum.inductiveautomation.com/u/cmallonee)\
**Post date:** [May 31, 2022, 2:58pm UTC](https://forum.inductiveautomation.com/t/browser-library-error/60198/4 "2022-05-31T14:58:55Z")

</div>

See also this thread: [[Bug-1203] Designer Chromium Crash with Exit Code 139 on MacOS Big Sur](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357)

It’s a known issue stemming from our use of JXBrowser. We’re actively waiting on a fix from them, but their last several releases have resolved _this_ issue but introduced a number of equally serious issues in other places. Until we can identify a desirable build from them we can’t do anything about this.

---

_[View the full topic](https://forum.inductiveautomation.com/t/browser-library-error/60198)._