topic Re: Qlik Sense Feb 2019 - Memory Leak Issue in Management & Governance

Qlik Sense Feb 2019 - Memory Leak Issue

robert_bond — Sat, 16 Nov 2024 06:29:07 GMT

We're experiencing a memory leak issue w/ February 2019 release. Our server has 160GB of memory. How do I troubleshoot this problem?

Re: Qlik Sense Feb 2019 - Memory Leak Issue

Giuseppe_Novello — Tue, 26 Feb 2019 18:48:03 GMT

I would start checking the engine logs and the last app that were open prior the memory escalating to that level. It should show some warnings. Logs : program data / qlik/sense/logs/engine/trace / system_engine.logs

Re: Qlik Sense Feb 2019 - Memory Leak Issue

Giuseppe_Novello — Tue, 26 Feb 2019 18:52:50 GMT

I would look into the engine logs> Programdata/qlik/sense/logs/engine/trace/system_engine.log, and check prior the warnings what apps where open.

Re: Qlik Sense Feb 2019 - Memory Leak Issue

Bastien_Laugiero — Wed, 27 Feb 2019 09:13:11 GMT

Hello,

The engine consuming lots of memory is usually due to two reasons:

High usage (Too many applications loaded in memory, too many large applications,...)
A specific application or operation in an application consuming quickly a large amount of memory

To determine which one of them is the one you will need to understand how quickly the memory has been consumed.

Was it increasing progressively throughout the day until it reached 100% or did it spike in a few minutes?

I usually use Performance Monitor to determine that (see https://support.qlik.com/articles/000004029)

But you can also use the operation monitor application for that.

So if it's a progressive consumption you are facing, you probably want to take a look if you have large applications in your environment and how many are being loaded throughout the day. Perhaps 160 GB is not enough anymore for the usage of your platform. There are also a number of optimization you can apply in the engine settings to reduce/control the memory consumption documented here https://help.qlik.com/en-US/sense/February2019/Subsystems/ManagementConsole/Content/Sense_QMC/edit-engine.htm

If it's spike then I would suggest using Telemetry to determine which application or operation consumed all the memory. Perhaps the application in question needs to be optimized. See https://support.qlik.com/articles/000044757

Hope this helps!

Re: Qlik Sense Feb 2019 - Memory Leak Issue

robert_bond — Fri, 01 Mar 2019 16:05:11 GMT

An update on this issue. We're still investigating. The best lead I have is that it might be an issue related to Nprinting. We have Nprinting and per our partner, they have seen this type of issue before. I will summarize my findings so that the community may benefit.

Re: Qlik Sense Feb 2019 - Memory Leak Issue

robert_bond — Mon, 20 May 2019 19:05:29 GMT

Update: This issue hasn't reoccurred, so I'm guessing it's not a problem anymore.