CPU pegged at 100%+ all the time, unable to nail down cause

Setup, Configuration and Use Scripts & Rules
, ,
15
  • Log into the karaf console
  • bundle:list | grep lsp

You should get something like

openhab> bundle:list | grep lsp
136 │ Active │  80 │ 0.10.0.v20201105-1103 │ org.eclipse.lsp4j
137 │ Active │  80 │ 0.10.0.v20201105-1103 │ org.eclipse.lsp4j.jsonrpc
  • Execute bundle:stop <bundle number> where <bundle number> is the value in the first column of results from the previous command for both bundles. Listing them again should show they are no longer active.
136 │ Resolved │  80 │ 0.10.0.v20201105-1103 │ org.eclipse.lsp4j
137 │ Resolved │  80 │ 0.10.0.v20201105-1103 │ org.eclipse.lsp4j.jsonrpc

I’m not certain if this is permanent or not but you could restart OH, disable them first thing and see if that addresses the problem. If not then it’s something else. If so we can explore how to disable it permanently.

3.2 is milestone releases. OH releases work as follows:

  • Release: every six months a new “stable” release is created. When there are no major breaking changes the release is treated as a point release. The current release is 3.1.

  • Milestone Releases/AKA Testing Releases: every month a new milestone release is created. These have no known major problems but problems sometimes come through. The current milestone release is 3.2 M1.

  • Snapshots: this is the bleeding edge and a new snapshot is created with the latest code merged into the baseline every day (unless the build breaks).

However, just because a baseline is called a release or a milestone doesn’t mean it’s completely free of bugs. Stable just means it’s not changing much for six months. Also, despite being on the bleeding edge, the snapshot releases are remarkably free from bugs almost all the time. Many of us run on the snapshots in our production system with only very rare problems. I personally run either a milestone version when my time is short or the snapshots when I have more time, upgrading the snapshot version a couple of times a week. Very rarely do I encounter any problems and because each upgrade include fewer changes over all, I end up spending less time dealing with breaking changes than I would had I stuck to the release versions and had to deal with six months of changes all at once.

So if you are encountering a problem with a milestone or release version and a fix exists in a snapshot I do not hesitate to recommend installing the snapshot version with the fix and stop upgrades of OH at least until the next milestone or release that includes the fix too.

File an issue on the openhab-core repo. See How to file an Issue for details.

Do you perhaps have an inadvertant circular reference somewhere in your load statements? I doubt Nashorn is smart enough to prevent that sort of thing. So if a.js loads b.js which loads c.js which loads a.js you’d end up in an infinite loop of loading.

Pay attention to both your code and the Helper Libraries as well.

1 Like