# \[Bug-1203\] Designer Chromium Crash with Exit Code 139 on MacOS Big Sur **URL:** \ **Category:** Ignition\ **Tags:** ignition80, perspective\ **Created:** [May 5, 2021, 3:16am UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357 "2021-05-05T03:16:18Z")\ **Posts on this page:** 17\ **Page:** 2
**Author:** ![milbar](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@milbar](https://forum.inductiveautomation.com/u/milbar)\ **Post date:** [November 30, 2022, 9:31pm UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/21 "2022-11-30T21:31:05Z")
Still getting this bug on 8.1.21 on Mac Pro running Ventura. Any updates? ---
**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:** [November 30, 2022, 9:37pm UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/22 "2022-11-30T21:37:26Z")
The previously-mentioned version from the JXBrowser team did not meet our requirements for adoption. We are looking into whether we can make changes on our end to accept it while we have also requested another version from them with fixes for the issues we encountered. Unlikely to have any more info before 8.1.25 as we've already begun on 8.1.24. ---
**Author:** ![wdougmiller](https://avatars.discourse-cdn.com/v4/letter/w/a9a28c/32.png) [@wdougmiller](https://forum.inductiveautomation.com/u/wdougmiller)\ **Post date:** [December 17, 2022, 8:13pm UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/23 "2022-12-17T20:13:48Z")
Following this thread as I just hit the same issue on my Mac. Was glad to find a thread on the forum for this issue, but it was a disappointing read. ☹ ---
**Author:** ![salbrechtsen](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/salbrechtsen/32/18660_2.png) [@salbrechtsen](https://forum.inductiveautomation.com/u/salbrechtsen)\ **Post date:** [January 6, 2023, 12:28am UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/24 "2023-01-06T00:28:25Z")
Same... Still having this issue years later and sometimes it causes a loss of work. ---
**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:** [January 6, 2023, 1:12am UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/25 "2023-01-06T01:12:06Z")
We hear you, and some of us feel the same pain you do from this bug. We are going to repair it as soon as is possible, but the timeframe for repairing it is frustratingly out of our control as we're dependent on a third-party product and we must be careful that repairing _this_ issue does not introduce something just as bad. ---
**Author:** ![milbar](https://avatars.discourse-cdn.com/v4/letter/m/d78d45/32.png) [@milbar](https://forum.inductiveautomation.com/u/milbar)\ **Post date:** [January 6, 2023, 2:17am UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/26 "2023-01-06T02:17:39Z")
I hate to break it to you but you come off as not really interested in the fact that we may loose hours of work due to this bug. Time is money and we lose it because of this. You seem to just be throwing your hands up and saying “its not our fault so just deal with it”. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [January 6, 2023, 3:04am UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/27 "2023-01-06T03:04:47Z")
> [@milbar](#): > > I hate to break it to you 🙄 You could always abandon the one architecture that seems to be plagued by this bug. If it really is costing you that much moola, you can justify switching to a better computer. /snark (though I think the emoji just doesn't properly convey how far back my eyes are rolling) ---
**Author:** ![WillMT10](https://avatars.discourse-cdn.com/v4/letter/w/7feea3/32.png) [@WillMT10](https://forum.inductiveautomation.com/u/WillMT10)\ **Post date:** [January 6, 2023, 9:15am UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/28 "2023-01-06T09:15:10Z")
At this point, I’m honestly less concerned about this particular designer bug and more concerned by the fact it’s going on 2 years - unless I missed a note somewhere - without a Jxbrowser update due to every release having major bugs. This means - besides eroding confidence that future major bugs will be fixable in a timely manner - that there are a whole lot of unpatched security vulnerabilities. I’ll be honest though, I don’t have a great understanding of where Jxbrowser is actually important to Ignition and how it might compromise a system. Is it only important to the designer and web browser component? It would be nice to get some additional insight into what level of concern should be attributed to having woefully unpatched Chromium versions deployed, even if only limited to machines that have the designer installed. If it’s not a viable attack vector, it would be great to get some insight into why. ---
**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\ **Post date:** [January 6, 2023, 10:38am UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/29 "2023-01-06T10:38:26Z")
Is this problem limited to _Big Sur_ or is it affecting newer operating systems as well? I run my designer from a Mac, and I haven't had a single problem, but my designer doesn't run directly from the OS; it's sandboxed in a VM. ---
**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\ **Post date:** [January 6, 2023, 11:37am UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/30 "2023-01-06T11:37:52Z")
For perspective, only the designer uses jxbrowser. And maybe there were updates to it, but just none that fixed your issue. Maybe you should ask Apple to fixed their laptop instead, since that is the problem xd Good luck getting a positive reply from them. i bet they'll just recommend buying a new expensive laptop, since they never rly fix things xd ---
**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:** [January 6, 2023, 4:46pm UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/31 "2023-01-06T16:46:22Z")
> [@justinedwards.jle](#): > > Is this problem limited to _Big Sur_ or is it affecting newer operating systems as well? I'm using Ventura and still encounter it regularly. ---
**Author:** ![WillMT10](https://avatars.discourse-cdn.com/v4/letter/w/7feea3/32.png) [@WillMT10](https://forum.inductiveautomation.com/u/WillMT10)\ **Post date:** [January 6, 2023, 4:51pm UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/32 "2023-01-06T16:51:27Z")
It’s not a MacOS bug. It’s a known bug in Jxbrowser. There have been updates to Jxbrowser that have supposedly fixed this particular MacOS issue. If you search the forum for “Jxbrowser update” you’ll see a number of different posts from IA developers saying each new update has had major bugs that prevent them from updating the Jxbrowser version that is packaged with Ignition. As far as I’m aware, this has been the case since - at a minimum - when I created this post. That would mean the Jxbrowser version with Ignition is at least 14 versions behind current - and by extension - a very old version of Chromium too. ---
**Author:** ![mcarritt1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mcarritt1/32/4262_2.png) [@mcarritt1](https://forum.inductiveautomation.com/u/mcarritt1)\ **Post date:** [June 5, 2023, 9:31am UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/33 "2023-06-05T09:31:41Z")
version 8.1.28 mentions an update to Jxbrowser, anyone have any details if that update addresses this mac os issue? ---
**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\ **Post date:** [June 5, 2023, 9:37am UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/34 "2023-06-05T09:37:35Z")
> [@mcarritt1](#): > > anyone have any details > [@Editing Perspective Styles in v8.1.27 Slower than before?](https://forum.inductiveautomation.com/t/editing-perspective-styles-in-v8-1-27-slower-than-before/73316/4): > > crossed_fingers ---
**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:** [June 5, 2023, 2:38pm UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/35 "2023-06-05T14:38:22Z")
It does remove that issue. It's fantastic. ---
**Author:** ![salbrechtsen](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/salbrechtsen/32/18660_2.png) [@salbrechtsen](https://forum.inductiveautomation.com/u/salbrechtsen)\ **Post date:** [June 7, 2023, 11:24pm UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/36 "2023-06-07T23:24:01Z")
Awesome. So glad this is fixed, will download the update today. ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [June 7, 2023, 11:26pm UTC](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357/37 "2023-06-07T23:26:58Z")
Just because I know this will come up... Only a Designer launched and running against an 8.1.28+ Gateway will have this fix. Designers are launched and with run binaries from whatever version of Ignition they are pointed at. Just because you downloaded a new Designer _Launcher_ from 8.1.28+ doesn't mean anything. You must upgrade each Ignition Gateway you will run the Designer against. [Previous page](https://forum.inductiveautomation.com/t/bug-1203-designer-chromium-crash-with-exit-code-139-on-macos-big-sur/46357.md?page=1)