# Browsercore64 gone wild **URL:** \ **Category:** Ignition\ **Created:** [February 23, 2020, 6:49pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523 "2020-02-23T18:49:15Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\ **Post date:** [February 23, 2020, 6:49pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/1 "2020-02-23T18:49:15Z")
Using Ignition 8.0.9 on Linux. After about 60 minutes of work, a view with a time series chart errored. After that browsercore64 went to 116% of CPU and stayed there until I shut down designer. ---
**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\ **Post date:** [February 23, 2020, 7:54pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/2 "2020-02-23T19:54:23Z")
This is what is locking up browsercore64: 11:52:02.538 [Browser Events Thread] INFO Perspective.Designer.BrowserConsole - [mobx] Encountered an uncaught exception that was thrown by a reaction or observer component, in: ‘Reaction[Reaction@10119]’ 11:52:03.463 [Browser Events Thread] INFO Perspective.Designer.BrowserConsole - [mobx] Encountered an uncaught exception that was thrown by a reaction or observer component, in: ‘Reaction[Reaction@10119]’ 11:52:04.349 [Browser Events Thread] INFO Perspective.Designer.BrowserConsole - [mobx] Encountered an uncaught exception that was thrown by a reaction or observer component, in: ‘Reaction[Reaction@10119]’ This occurs about every 0.9 seconds. I haven’t a clue on how to debug this… ---
**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\ **Post date:** [March 2, 2020, 8:04pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/3 "2020-03-02T20:04:30Z")
For anyone checking out this thread. Support is still working one it. It occurs on both Windows and Linux designers (although the browser core has a different name). It seems to be related to the synchronization step when opening the view in designer. With a complicated time series chart (multiple series with multiple trends) it locks up about 75% of the time upon opening the view. It does not lock up when opening the view as a client. This problem started at 8.0.8 and still exists in 8.0.9. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 2, 2020, 8:06pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/4 "2020-03-02T20:06:27Z")
Are you able to try nightly builds? The 8.0.11 nightly that’ll be available tomorrow has a fix that may resolve this. ---
**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\ **Post date:** [March 2, 2020, 8:22pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/5 "2020-03-02T20:22:13Z")
I have a development platform I can test it on ---
**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\ **Post date:** [March 2, 2020, 10:31pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/6 "2020-03-02T22:31:45Z")
Paul, I had a breakthrough with my testing. It is not the time series chart that is throwing the error. It is the tag history binding to an expression that is causing the error. I can create the problem without a chart. ---
**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\ **Post date:** [March 2, 2020, 11:51pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/7 "2020-03-02T23:51:32Z")
The expression has nothing to do with it. I can create the same effect with a direct tag history binding. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 3, 2020, 1:22am UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/8 "2020-03-03T01:22:40Z")
There’s a bunch of ways to hit it, if it’s the bug I think it is - it’s apparently something fairly fundamental in Perspective, so it can happen in a bunch of different ways. Like I said, we’ve identified (at least one source) of problems, and fixed that in 8.0.10, so you can try the RC or the 8.0.11 nightly that’ll be up tomorrow. ---
**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\ **Post date:** [March 3, 2020, 5:41pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/9 "2020-03-03T17:41:13Z")
Paul, I don’t see 8.0.10-RC1 but I do see 8.0.11 Nightly. I would prefer to use a release candidate since they are typically more stable. Is it coming out today or do I need to use the 8.0.11-Nightly? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 3, 2020, 5:48pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/10 "2020-03-03T17:48:21Z")
It’ll be out very soon - I can’t promise today, but almost certainly this week. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 4, 2020, 10:02pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/11 "2020-03-04T22:02:21Z")
8.0.10 RC1 is up on the website now. [https://inductiveautomation.com/downloads/ignition/8.0.10-rc1](https://inductiveautomation.com/downloads/ignition/8.0.10-rc1) ---
**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\ **Post date:** [March 5, 2020, 12:51am UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/12 "2020-03-05T00:51:14Z")
Unfortunately, this RC did not fix the problem. (Thankfully it did fix some other big ones.) I can reproduce this error any time you would like to watch. ---
**Author:** ![weertske](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/weertske/32/3353_2.png) [@weertske](https://forum.inductiveautomation.com/u/weertske)\ **Post date:** [March 6, 2020, 8:42pm UTC](https://forum.inductiveautomation.com/t/browsercore64-gone-wild/32523/13 "2020-03-06T20:42:52Z")
@paul-griffith I need to retract that, it did fix the problem in a roundabout way. What was causing the chart to lock up was triggered by multiple items a lot of which were fixed by this release. However, one binding to calculate the max for one of the trends was also contributing to the problem. However, as a part of 8.0.10-rc1, the time series chart will automatically calculate the max for a chart. Therefore, I do not need that binding. With its removal plus the improvements made to this release, the charts are now working and no longer locking up. I do believe there are some underlying issues waiting to break later especially in regards to basic datasets as a part of json. But, for now, I consider this case solved. Thank you for your help.