CPU Usage High and Qlik Sense Crashes

[d_prashanthredd]

Hi,

When I open Qlik Sense Desktop, my CPU Usage is going to the limit >50% and sometimes it goes to 100% and crashing very often. Observed that there are so many/multiple processes running for Qliksensebrowser.exe (Qliksense Browser), node.exe (Node.js: Server -side JavaScript) and conhost.exe (Console Window Host).

Note: Count for node.exe and conhost.exe is more than 10.

Is this appropriate or something wrong?

[rittermd]

Are you saying that this happens when you just open QS Desktop?  I would understand this if you opened an app or were doing a reload. 

I have seen this happen when reloading if your data model is not clean.

[JustinDallas]

Have you looked at the Logs? I'm not sure what I would expect to be there, but you should be able to find something with a Logging Level of 'ERROR'.?

[d_prashanthredd]

Hi Mark,

When I open qliksense, sometimes it is going to 20% and above and when I

open any app its around 40% but it is not happening always.

My reloads and other stuff is happening in seconds. In edit mode when

change layout or drag and drop or if I edit or add any measure.

Im sure that my data profiling is good as I'm a SQL developer.

Those three processes are running multiple times on just opening itself.

[rittermd]

What is the configuration of your computer?

I just tried it on my laptop.  I do see a spike in CPU when QS opens to about 48%.  Then once it is open it drops back down to 4%-6%.

My QlikSenseBrowser is using 24MB of RAM.

So I am guessing that what you are seeing is probably normal.

[d_prashanthredd]

Exactly Mark,

For last 3 months I'm working on the same app and never faced any issue but

for last 1 week, seeing this that too not always. I can say today 3-4 times

it crashed and sometimes reached to high CPU usage.

Note that it is not happening every time. And multiple processes are

running every time.

My laptop configuration - 20 GB ram, core i7.

[rittermd]

What version of QS Desktop are you running?

[rittermd]

Is it possible you installed some Windows updates in the past week or so that might be causing an issue?