Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Memory Leak Bug on Qlikview Server Version 9 SR 2?

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

34 Replies
StefanBackstrand
Partner - Specialist
Partner - Specialist

Footsie;

Well, are you really sure you can access all memory on your box? You have a physical commit ~4 GB (if roughly adding the Private Bytes column), and yet the "Physical Usege %" in the bottom pane says 87.5%. 4 GB is not 87% of anything near 12 GB.

It sounds like you have a 32 bit (x86) box with too much RAM in it for your Windows architecture to handle. Can you supply a screenshot of the Performance tab in Task Manager?

Not applicable
Author

Hi Stefan,

Please find attached a copy of the performance tab from taskmgr.

Please also find some system info from the system information tab in Qlikview

======================= Local System Info ========================
Operating System Windows Server 2008 R2 Standard (64 bit edition)
Operating System Version 6.1.7600
Wow64 mode Not using Wow64
IE Version 8.0.7600.16385
MDAC Version 6.1.7600.16385
MDAC Full Install Version 6.1.7600.16385
ComCtl32 version 6.16.7600
Current Theme Classic (No theme active)
Graphics 1 1280*1024 pixels. 1 Monitors.
Graphics 2 16 Bit Color Depth. 96 XDpi. 96 YDpi.
Local Time 2010-08-16 15:02
GMT Time 2010-08-16 14:02
Country
Language
Physical RAM(MB) 16383
VMCommitted(MB) 173
VMAllocated(MB) 251
VMFree(MB) 8388357
VMLargestFreeBlock(MB) 8379101
Number of CPUs 2
CPU 0 Intel(R) Xeon(R) CPU X7350 @ 2.93GHz 2932MHz
CPU 1 Intel(R) Xeon(R) CPU X7350 @ 2.93GHz 2932MHz

Kind Regards

Footsie

StefanBackstrand
Partner - Specialist
Partner - Specialist

This is just getting more and more weird.

Before we go any further to register a support case, please can you supply the following?

1. Performance data from Task manager (Performance tab) and Process explorer during the peak of the reload
2. Performance data from Task manager (Performance tab) and Process explorer after the reload

The memory has got to show somewhere.

Not applicable
Author

Hi Stefan,

Yes it is a strange issue alright.

I have already logged a case with Qlikview Support. The case ID is 00031280. I posted on the forum as well to see if anyone else had encountered a similar issue. The performance tab stays the same after the reload ie it does not free up the RAM. Please find attached a screenshot of the Processes tab.

Kind Regards,

Footsie

Not applicable
Author

Thanks for all your assistance on this issue Stefan.

The Qlikview Server was a virtual machine. VMWare memory reservation (Memory balooning) "stole" the memory, thus not showing it in the Task Manager or Process Explorer. I have disabled that, and it now runs fine.

Thanks and Regards,

Footsie