Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

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

1 Solution

Accepted Solutions
ggg
Contributor II

Memory Leak Bug on Qlikview Server Version 9 SR 2?

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

34 Replies
ggg
Contributor II

Memory Leak Bug on Qlikview Server Version 9 SR 2?

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

Not applicable

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Gustav,

Thank you for your response. That was very helpful.

Don

ggg
Contributor II

Memory Leak Bug on Qlikview Server Version 9 SR 2?

Hi Don,

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

Regards,

Gustav

jsomsen
Contributor III

Memory Leak Bug on Qlikview Server Version 9 SR 2?

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.

ggg
Contributor II

Memory Leak Bug on Qlikview Server Version 9 SR 2?

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

twebber
Contributor II

Memory Leak Bug on Qlikview Server Version 9 SR 2?

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)

ggg
Contributor II

Memory Leak Bug on Qlikview Server Version 9 SR 2?

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

Employee
Employee

Memory Leak Bug on Qlikview Server Version 9 SR 2?

I agree with Gustav.

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

Not applicable

Memory Leak Bug on Qlikview Server Version 9 SR 2?

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?

Community Browser