Memory Leak Bug on Qlikview Server Version 9 SR 2?

[#1]

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

[StefanBackstrand]

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.

[#3]

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

[StefanBackstrand]

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

[StefanBackstrand]

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?

[#6]

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

[StefanBackstrand]

/err

[#8]

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

[StefanBackstrand]

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. 😃

[#10]

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

[StefanBackstrand]

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.