topic Memory Leak Bug on Qlikview Server Version 9 SR 2? in QlikView

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Mon, 26 Jan 2026 18:19:17 GMT

We've been monitoring the Max VM Committed by Day chart on the Qlikview Operations Monitor Server tab for the past several weeks after we upgraded from V8.5 to V9 R2 in early December 2009.. The VM grows each day until it reaches a maximum peak after several days and then crashes the QVS service bringing down the server. Restarting the QVS service clears the VM only for it to start growing again. The process continues to repeat itself. Shouldn't Qlikview swap out VM when it doesn't need it. This looks like a memory leak to me. We have a 64 bit server with 24GB of RAM which should be plenty. We increased our paging file to 12GB, but the VM will grow to that level in a few days only to crash again.

Is anyone else experiencing this problem? Any suggestions? Thanks.

Don Saluga

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Gustav_Guldberg — Wed, 06 Jan 2010 23:48:03 GMT

Hi Don,

This sounds like a known bug to me. The description fits pretty well with the virtual memory not being released.
Customer patch 9.00.7336 (will also be included in the SR3 release).

Open a case with QlikView Support and request the patch (simple QVS.exe switch) and see if that helps.

Regards,

Gustav

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Thu, 07 Jan 2010 14:31:00 GMT

Gustav,

Thank you for your response. That was very helpful.

Don

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Gustav_Guldberg — Thu, 07 Jan 2010 14:46:23 GMT

Hi Don,

Shoot an email to support@qlik.com and I'll assist you in getting the patch.

Regards,

Gustav

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Anonymous — Mon, 26 Apr 2010 21:08:53 GMT

Does anyone know if this is still an issue in SR3? We seem to be having the same issue. We are running on Win Server 2008 R2 and not sure if that would be normal.

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Gustav_Guldberg — Thu, 29 Apr 2010 15:51:18 GMT

Hi,

I have not had any reports saying that this issue exists in QVS SR3 7440.
If you believe that you have an issue in 7440 with virtual memory not being released properly I would recommend opening up a support case describing the issue in detail so that we can look into it. Do you see the virtual memory growing in the event-log for QVS?

Regards,

Gustav

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Anonymous — Thu, 22 Jul 2010 14:45:29 GMT

I think we have memory issues with SR3. I am using build 9.0.7440.8. We have a document that is about 200megs when loaded in memory. QVS.exe will grow to over 200megs when its open and that memory will not be released after the document is closed. The document is never preloaded into memory and there is only one copy allowed in memory at a time.

I'll start a new post for this under the heading SR3 Memory Issue (9.0.7440.8)

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Gustav_Guldberg — Thu, 22 Jul 2010 15:45:06 GMT

Tim,

The document will unload from memory after 480 minutes by default, not when the session closes.
This is the expected behavior and has to do with the Working Set Limits and product design.

A document that uses 200 mb in loaded state will use more once the user starts doing calculations.

What you are describing seems very normal.

Regards,

Gustav

Memory Leak Bug on Qlikview Server Version 9 SR 2?

StefanBackstrand — Fri, 23 Jul 2010 10:51:09 GMT

I agree with Gustav.

Tim, see Johannes conclusion and my additions on this; http://community.qlik.com/forums/p/31857/123093.aspx#123093.

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Tue, 10 Aug 2010 22:27:03 GMT

We recently upgraded to Verison 9.0 SR2 and we are experiencing performance problems. The cpu is consumed to 92%+ by the qvs.exe and doesn't allow any other processes to peform well.

Has anyone seen this problem and have any ideas on a solution?

Memory Leak Bug on Qlikview Server Version 9 SR 2?

StefanBackstrand — Wed, 11 Aug 2010 08:52:56 GMT

timdew: Even though I don't know if the later SR's have a fix for a specific CPU usage problem, I would strongly recommend upgrading to SR5.

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Wed, 11 Aug 2010 12:25:35 GMT

Stefan: We are already on 9.00.07502.8 release and I am pretty sure this is SR5 x64 bit version....

Memory Leak Bug on Qlikview Server Version 9 SR 2?

StefanBackstrand — Wed, 11 Aug 2010 13:27:47 GMT

Ok, cause you wrote that you upgraded to version SR2 in the post above.. ?

Memory Leak Bug on Qlikview Server Version 9 SR 2?

StefanBackstrand — Wed, 11 Aug 2010 13:29:13 GMT

Anyways;

Are you using pre-load in QVS?

When does QVS use the CPU?

How many cores are there in the server? Hardware specs? Memory amount?

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Wed, 11 Aug 2010 14:37:20 GMT

Stefan: Sorry about that "SR5", it was a typo... my mistake.

anyway, not sure if we are or not pre-loading in qvs????

After we open the application and click on the dashboard page. We suspect the appplication can be improved in the script and we'll look into that this morning.

4 dual core processors (8), 256GB, server 2008 enterprise edition (64 bit).

Tim

Memory Leak Bug on Qlikview Server Version 9 SR 2?

StefanBackstrand — Wed, 11 Aug 2010 15:54:37 GMT

/err

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Wed, 11 Aug 2010 20:19:01 GMT

No - we are no pre-loading. We are experiencing so many problems... we decided to turn it off.

Memory Leak Bug on Qlikview Server Version 9 SR 2?

StefanBackstrand — Thu, 12 Aug 2010 08:02:25 GMT

timdew;

Pre-loading is defined per document in QVS to lighten the initial load of users viewing documents. If you are not familiar with it, I guess you don't use it, since it is not default.

If you are having a 4 cpu dual core machine with 256 gb ram working on a dashboard for a sustained period of time (I guess that this is > 1 minute), I would say that you definately need to look over the charts and tables on the "Dashboard" sheet in your document. Maybe not neccessary your QV script.

The time your are experiencing when clicking on a sheet is the render time for the objects (charts, listboxes and so on) over the data currently active in your session in the document. If that takes this amount of time, somethings probably wrong - or we have a HUGE bug. My experience tells me it is the first of these two. 😃

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Thu, 12 Aug 2010 08:59:16 GMT

Hi Folks,

I am experiencing something similar on a Windows 2008 SR 2 64 bit server running Qlikview Server SR 5 and Publisher Enterprise. The server has 16 GB of RAM. Once one of the reload jobs starts on the server the RAM increases to around 13GB-14GB and does not release this memory until the server is restarted. Any additional jobs that run after this are very slow. I cannot see which process that the RAM is being consumed by if I run taskmgr. Has anyone seen this issue or something similar. It looks like a memory leak.

Kind Regards,

Footsie

Memory Leak Bug on Qlikview Server Version 9 SR 2?

StefanBackstrand — Thu, 12 Aug 2010 09:59:25 GMT

Footsie;

Are you sure you cannot see what process is responsible for the memory usage?

In 2008, use the Task Manager, go to the Processes tab, open the menu View > Select columns.., and make sure that the column "Working set (Memory)" is selected. If you sort descending (highest first) on that, you will find what process is using your memory.