Solved: Re: Anyone notice a memory leak in Qlikview 11 - Qlik Community

mellerbeck · ‎2012-01-03

It appears that after a couple of weeks?? the Qlikview server service stops. If you restart the service everything is good.... for a while

StefanBackstrand · ‎2012-01-06

No, a "memory leak" is when memory is not returned to the system. Qlikview uses as much memory as possible for a reason, and hence keeps it for future use. Memory pages are then deallocated when qvs needs more within its working set. That does not necessary occur at a timeout, but at demand from the system.

If qvs is not recovering, you have a too high growth, too much objects and/or documents or badly designed documents. "Memory leaks" are rarely found in Qlikview.

View solution in original post

StefanBackstrand · ‎2012-01-04

Can you be more specific? What do you mean by "stops"? What are the symptoms? What does the QVS logs say? What does the Windows event logs say?

Report Inappropriate Content · ‎2012-01-04

I'm not sure its memory leak but more like memory not being recovered which is a problem I get in v9sr4.

My solution is to set a batch file to restart QVS which is run by Windows Scheduler nightly:

@echo off

net stop "QlikView Server"

ping -n 31 127.0.0.1 > NUL

net start "QlikView Server"

Regards,

Gordon

mellerbeck · ‎2012-01-06

Exactly Gordon! I think we had this in version 8.2, and 9. I think it got fixed in 10, but appears to come back in 11.

mellerbeck · ‎2012-01-06

Hi Stefan, I didn't dive into it too deeply. I was just curious if it had happened to anyone else. It's hard to catch it in the act. This might be it?

The description for Event ID 300 from source QlikViewServer cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Restart: Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type D, detected.

***********************

Faulting application name: QVS.exe, version: 11.0.11149.0, time stamp: 0x4ec5045e

Faulting module name: QVS.exe, version: 11.0.11149.0, time stamp: 0x4ec5045e

Exception code: 0xc0000005

Fault offset: 0x0000000000c077e6

Faulting process id: 0x19d4

Faulting application start time: 0x01ccca37640cda45

Faulting application path: C:\Program Files\QlikView\Server\QVS.exe

Faulting module path: C:\Program Files\QlikView\Server\QVS.exe

Report Id: 41129790-37cd-11e1-94c4-001a6435566e

***********************

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: QVS.exe

P2: 11.0.11149.0

P3: 4ec5045e

P4: QVS.exe

P5: 11.0.11149.0

P6: 4ec5045e

P7: c0000005

P8: 0000000000c077e6

P9:

P10:

Attached files:

C:\Users\ITService\AppData\Local\Temp\WER7D89.tmp.appcompat.txt

C:\Users\ITService\AppData\Local\Temp\WER7DD8.tmp.WERInternalMetadata.xml

C:\Users\ITService\AppData\Local\Temp\WER9235.tmp.mdmp

C:\Users\ITService\AppData\Local\Temp\WER92C2.tmp.WERDataCollectionFailure.txt

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_QVS.exe_44d28bc3dc0ac164b44db2591705b46c967f945_cab_627c933b

Analysis symbol:

Rechecking for solution: 0

Report Id: 41129790-37cd-11e1-94c4-001a6435566e

****************************

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: QVS.exe

P2: 11.0.11149.0

P3: 4ec5045e

P4: QVS.exe

P5: 11.0.11149.0

P6: 4ec5045e

P7: c0000005

P8: 0000000000c077e6

P9:

P10:

Attached files:

C:\Users\ITService\AppData\Local\Temp\WER7D89.tmp.appcompat.txt

C:\Users\ITService\AppData\Local\Temp\WER7DD8.tmp.WERInternalMetadata.xml

C:\Users\ITService\AppData\Local\Temp\WER9235.tmp.mdmp

C:\Users\ITService\AppData\Local\Temp\WER92C2.tmp.WERDataCollectionFailure.txt

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_QVS.exe_44d28bc3dc0ac164b44db2591705b46c967f945_cab_627c933b

Analysis symbol:

Rechecking for solution: 0

Report Id: 41129790-37cd-11e1-94c4-001a6435566e

Report Status: 4

StefanBackstrand · ‎2012-01-06

We've seen no clear signs of memory leaks in 11 yet. They are usually by design behavior in the core. Using lots of memory, and caching for future use, is one of the strengths of the QV core.

The internal inconsistencies errors might point to the fact that memory is exhausted. If not, it's classified as a bug. Have any meme statistics in the machine globally during the error? If not, get some for the next round.

mellerbeck · ‎2012-01-06

If memory is exhausted isn't that a memory leak

I don't know how to check if 'any meme statistics in the machine globally during the error?'

StefanBackstrand · ‎2012-01-06

No, a "memory leak" is when memory is not returned to the system. Qlikview uses as much memory as possible for a reason, and hence keeps it for future use. Memory pages are then deallocated when qvs needs more within its working set. That does not necessary occur at a timeout, but at demand from the system.

If qvs is not recovering, you have a too high growth, too much objects and/or documents or badly designed documents. "Memory leaks" are rarely found in Qlikview.

mellerbeck · ‎2012-01-06

Ah that makes sense! Thanks. Whats the best way to monitor for this sort of thing

prieper · ‎2012-01-18

Hmm,

noticed very similar. Now after a normal workingday and with no document left in memory, the QVS still keeps 15GB of RAM. Admittingly no memory is needed yet.

Via batches the QVS is restarted daily at midnight.

QVS-version: 11-11154.

++

Peter