ERROR [frontend.js.latest.202112290] core.360c502d.js:1:9840 3

[Mariusthvdb]

Checklist

• [X] I have updated to the latest available Home Assistant version.
• [X] I have cleared the cache of my browser.
• [X] I have tried a different browser to see if it is related to my browser.

Describe the issue you are experiencing

not even experiencing an issue, but this keeps showing I the log. Really sorry I havent been able to connect it to a user action, but there's no true clue how to go about debugging this further without instructions

Describe the behavior you expected

no error....

Steps to reproduce the issue

1. as said, not sure

3. ...

What version of Home Assistant Core has the issue?

2022.2.0.dev20220103

What was the last working version of Home Assistant Core?

not sure but at least the last week of dev

In which browser are you experiencing the issue with?

any

Which operating system are you using to run this browser?

MacOS 12.0.1 12.0.1 Monterey 12.0.1

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

2022-01-03 10:06:14 ERROR (MainThread) [frontend.js.latest.202112290] https://mydomain/frontend_latest/core.360c502d.js:1:9840 3

Additional information

No response

[tempus2016]

I too am getting this error.

Logger: frontend.js.latest.202112290
Source: components/system_log/__init__.py:189
First occurred: 22:35:12 (1 occurrences)
Last logged: 22:35:12

https://XXX/frontend_latest/core.360c502d.js:1:9840 3

[Mariusthvdb]

still seeing this in 2202.2.0b0 so not a dev install fluke, purposely updated to the beta to check.

[spacegaier]

still seeing this in 2202.2.0b0 so not a dev install fluke, purposely updated to the beta to check.

Can you please provide the exact error location now with the beta. I should have the same, so perhaps we can narrow down the error based on the code location, even though the coding is minified.

[Mariusthvdb]

it moved to:

frontend_latest/core.9023daf4.js:1:9840 3

in my setup

[spacegaier]

So that means it is that green line here, which I think is from home-assistant-js-websocket.

[Mariusthvdb]

tbh, I dont understand where you see that? But, now I check inspector again, I see the error being listed again. Could it be this happens upon loading Inspector??

not sure but I can see this:

which is dashboard 19 ..?

[spacegaier]

I just looked in the coding of that JS file at the location specified in the error message (line 1, position 9840) and then "prettied" the coding.

[Mariusthvdb]

not sure what you're saying now, do you mean you have a 'fix'? or do you want me to do anything?

also, which dashboard is 19 referring to? how can I count my dashboards?

[spacegaier]

No fix and nothing to do. Someone else needs to chime in to narrow down the issue. Some connection seems to break and then the error gets raised.

That is line 19, column 6545 in dashboard file (I think). You can click on it.

[balloob]

@Mariusthvdb the "Verzoek" bit, is that from an addon called logviewer served via ingress? I can't see the full URL.

And did you re-open the dashboard before this error occurred ?

[Mariusthvdb]

yes it is, https://github.com/hassio-addons/addon-log-viewer and is up to date 0.12.2

but it has become way more sporadic... I've only seen it once since this mornings update to latest dev build, and it moved to core.25b6fb5a.js:1:9840 3

even tried with 2 windows now, both on Logviewer didnt make it happen. so a bit of a mystery.

[Mariusthvdb]

right, so this is odd, I see logviewer:

2022-02-04 10:04:38 ERROR (MainThread) [frontend.js.latest.202202030] http://hassio.local:port/frontend_latest/core.9a12ab6a.js:1:9840 3

but also:

note 9840 is now 9841? Or is this something else (has always been 9840 until now)

clicking that results in:

full text of that section is enclosed frontend_error.txt

[bramkragten]

It means that something (browser-mod?) was sending a message to the backend, but the connection was closed.

It looks like this is from a custom card, and not core frontend.

[Mariusthvdb]

yes, this one indeed, the others were from logviewer though?

[bramkragten]

Could this be happening when the HA tab is hidden/inactive for 5 minutes? Can you maybe turn off "auto close connection" option and see if it is gone then?

[Mariusthvdb]

sure, will try. this is a per browser setting isnt it? as is the error probably?

btw, its back in some higher frequency:

Logger: frontend.js.latest.202202030
Source: components/system_log/__init__.py:190 
First occurred: 10:04:38 (24 occurrences) 
Last logged: 14:03:15

http://hassio.local:port/frontend_latest/core.9a12ab6a.js:1:9840 3
:0:0 Script error.

and on 9840 ;-)

logviewer:

2022-02-04 14:09:07 ERROR (MainThread) [frontend.js.latest.202202030] http://hassio.local:port/frontend_latest/core.9a12ab6a.js:1:9840 3
2022-02-04 14:09:07 ERROR (MainThread) [homeassistant.components.hassio.handler] /ingress/validate_session return code 401
2022-02-04 14:09:07 ERROR (MainThread) [homeassistant.components.hassio] Failed to to call /ingress/validate_session - 

and I do see ResizeObserver loop completed with undelivered notifications.

accompanied by:

022-02-04 15:04:47 ERROR (MainThread) [frontend.js.latest.202202030] :0:0 Script error.

on each keystroke c/e, to call the quick bar

guess its not the close connection setting:

Logger: frontend.js.latest.202202030
Source: components/system_log/__init__.py:190 
First occurred: 10:04:38 (33 occurrences) 
Last logged: 15:05:31

http://hassio.local:port/frontend_latest/core.9a12ab6a.js:1:9840 3
:0:0 Script error.

[Mariusthvdb]

not really sure the issue @zacwest linked above it the issue at hand here. As Ive been trying to narrow down the source, I disabled Kiosk Node plugin, and havent seen the error since. Would be nice if people that responded with a +1 here could check/confirm they also use Kiosk mode, and if yes, when disabled see the error gone?

I filed 2 issues before in Kiosk mode, maybe these are related. Bram might be able to recognize the error and its meaning?

https://github.com/maykar/kiosk-mode/issues/84 https://github.com/maykar/kiosk-mode/issues/75

Seems Ryan has left the repo for some time now, not sure if maintenance will be up anytime soon there

[skynet01]

@Mariusthvdb I think you are right, I have Kiosk Mode plugin installed and removing it solved this issue for me

[tempus2016]

I do not use kiosk mode and have the error.

[Mariusthvdb]

I am afraid you're right... just updated to todays nightly and see

2022-02-10 08:42:47 ERROR (MainThread) [frontend.js.latest.202202030] http://mydomain/frontend_latest/core.9a12ab6a.js:1:9840 3

in the startup log again. too bad. it has become less frequent, but now we can say for sure Kiosk mode doesnt cause it. thats a good thing ;-)

[skynet01]

Hahah yea.. same for me. It came back today even with kiosk uninstalled.

[maddeuce]

Logger: frontend.js.latest.202202030 Source: components/system_log/init.py:190 First occurred: 9:26:21 PM (7479 occurrences) Last logged: 9:51:26 PM

:0:0 Script error.

This is the same error?

[maddeuce]

I have this error for couple months now no one can tell me what wrong. Everyone say is frontend intergradion. Will guess what I turn off all off and still happen. Usually it happen once or twice for 2 to 10 minutes per day but log up to 200k errors. But I just notice 3hrs ago it been reoccurring non stop. It slow down about 10 error per sec. Before I seem up to 5000 error per sec. At one time my homeassistant.log file is 125mb. That an txt file 125mb fill with this error log.

[Mariusthvdb]

its still a bit of a mystery indeed. I recently discovered it even happens when all front-end device are closed, so no HA interface is showing anywhere. How could a frontend error fire at all. I then, accidentally, noticed the error happening when I called 'Hey google, do..' Thought I had found the issue, because ofc we do that also when all devices are closed. But, unfortunately, it didnt reproduce reliably after that...

so still at a loss as for the reason this keeps happening.

Maybe it's a timing issue too, and we can prevent it from happening by loading a custom card via the frontend method. I have just done so with Kiosk mode, and haven't seen any of the Kiosk mode related errors since that, same https://github.com/maykar/kiosk-mode/issues/84#issuecomment-1041446352

EDIT

Never mind.... they're back.

[Mariusthvdb]

Logger: frontend.js.latest.202204200
Source: components/system_log/__init__.py:190 
First occurred: 10:31:46 (647 occurrences) 
Last logged: 10:47:56

http://hassio.local:port/frontend_latest/core.8ff2e18e.js:1:10023 3
:0:0 Script error.

[pedolsky]

I get a bunch of errors of the same source after editing automations:

Logger: frontend.js.latest.202205041
Source: components/system_log/__init__.py:190 
First occurred: 22. Mai 2022, 22:00:27 (99 occurrences) 
Last logged: 06:45:42

:0:0 Script error.

[maxshcherbina]

Im getting the following errors:

Logger: frontend.js.latest.202205041
Source: components/system_log/__init__.py:190
First occurred: May 22, 2022 at 7:30:38 AM (19 occurrences)
Last logged: 8:25:13 AM

http://192.168.1.118:8123/frontend_latest/core.a0afd420.js:1:9430 Uncaught Error: Suspend promise not set
https://home.maxistviews.com/frontend_latest/core.a0afd420.js:1:10014 Uncaught 3

[fenty17]

My logs are plagued by this sort of error. Tried removing cards with more complex cofigs but didn't work. Seems to happen when opening the app or browser reload (but not when cached).

Logger: frontend.js.latest.202205041
Source: components/system_log/__init__.py:190 
First occurred: 20:10:58 (7 occurrences) 
Last logged: 21:24:46

http://192.168.1.120:8123/frontend_latest/core.a0afd420.js:1:10024 3

[phiberoptick]

I'm a little late to the party but am having the same issue. I finally noticed it when I decided to try to look into why my Eufy integration stopped working recently and came across this in my logs.

Logger: frontend.js.latest.202206010
Source: components/system_log/__init__.py:190
First occurred: 10:47:43 (7 occurrences)
Last logged: 23:28:56

https://ha.devnulls-bitbucket.com:8123/lovelace:0:0 Uncaught
https://ha.devnulls-bitbucket.com:8123/lovelace/0:0:0 Uncaught
https://ha.devnulls-bitbucket.com:8123/developer-tools/yaml:0:0 Uncaught
https://ha.devnulls-bitbucket.com:8123/config/dashboard:0:0 Uncaught

[cplagz]

I had a similar issue when trying to edit cards on Lovelace UI - ending up needing to remove BrowserMod integration and problem went away.

Source: components/system_log/__init__.py:190
First occurred: 10:35:08 AM (13 occurrences)
Last logged: 10:35:08 AM

http://HA.URL:8123/frontend_latest/core.446aadfa.js:1:10014 Uncaught 3 ```

[Mariusthvdb]

currently in beta 2022.8 and seeing the same error, but now also on the Nabucasa link:

Logger: frontend.js.latest.202207280
Source: components/system_log/__init__.py:227 
First occurred: 18:36:08 (3 occurrences) 
Last logged: 23:03:41

https://t97redacted3o.ui.nabu.casa/frontend_latest/core.6ade3ee1.js:1:10024 3
http://hassio.local:myport/frontend_latest/core.6ade3ee1.js:1:10024 3

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Mariusthvdb]

I've gotten tired of all of these unexplained and unfixed Frontend errors, I finally decided to filter them in the home assistant log:

logs:
  frontend.js.latest: fatal

and be done with it.

[steverep]

Is this not a duplicate of #9022?

[Mariusthvdb]

No that is about the ResizeObserver explicitly ?

[halsafar]

Happening still in [frontend.js.latest.202305033].

[steverep]

Source maps have been improved since this was first reported. Browser console should have a full stack trace now. Someone please paste it here.

[bcutter]

Seing similar errors massively in HA log (starting with HA Core 2023.4.6):

Logger: frontend.js.latest.202304111
Source: components/system_log/__init__.py:257
First occurred: 6. November 2023 um 16:27:12 (1193 occurrences)
Last logged: 16:29:25

:0:0 ResizeObserver loop completed with undelivered notifications.
:0:0 Script error.
http://my-home-assistant:8123/frontend_latest/core--AdzVoB_i-0.js:1:9860 Uncaught Error: Suspend promise not set

Not sure what causes this or how to track down the root cause. Seing this old issue (and there are even older ones like https://github.com/home-assistant/core/issues/58567) doesn't really look well tbh.

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[bcutter]

Not stale :-(

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[silamon]

I just found these errors coming from the quickbar. Opening quickbar and then remove the ">" will trigger them both.

[steverep]

I just found these errors coming from the quickbar. Opening quickbar and then remove the ">" will trigger them both.

Which errors exactly? This issue thread has a mixed bag of errors, and the OP was filed before stack traces were significantly improved. IMO, this one should be closed unless the original can be reproduced with a full stack from the core entrypoint.

The ResizeObserver errors are harmless and covered by #9022 which we can reopen if needed. If we converted all observers to use @lit/observers for better tear down, I'd bet most of them would go away.

[silamon]

I should have specified further, but talking about the ResizeObserver error and Script 0:0 error. I did investigate further and indeed harmless, caused by increasing height of the items in the list. (For example, a one line item would become a two line item and then causes the height to increase causing a re-resize while the current resize is still calculating.)

[bcutter]

Closed, okay -.-

[silamon]

Closed, okay -.-

If you encounter these errors and you can reproduce them on a specific page, feel free to open a new issue.