Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
smoon63
Partner - Creator
Partner - Creator

QEMC Memory Leak

I am configuring a new QV9 64-bit Enterprise Server (SR1 v9.0.7257.6)8 on a VMWare ESX virtual machine. The VM is running Windows Server 2003 Standard x64 Edition SP2 on a Quad-Core AMD Opteron CPU and has 3.75GB RAM.

Yesterday I had the QEMC open to the Status\Tasks tab and had a task that had failed selected under the QDS tree. I left it unattended in that state for about an hour. When I came back to the server there was an error message to the affect of "not enough memory for this operation."

I thought that was odd considering that the machine is still being configured and is not being accessed by users at all. I opened Windows Task Manager to the Performance tab and the total Commit Charge was over 4GB. Switching to the Processes tab, I found an instance of iexplore.exe *32 running and holding well over 2GB of memory.

I closed the IE window containing QEMC and the memory usage dropped back to near its baseline number. I opened it back up to the same place and state as before while watching the Processes tab in Task manager. I have the Tasks tab set to "Automatic refresh of task list" and noticed that each refresh was bumping up the IE memory total by 3-4 MB per cycle. With the refresh running every 5 seconds, it obviously doesn't take long to eat up 3.75GB.

I have repeated the scenario (without letting it run to memory exhaustion) again this morning with the same result. I also noticed that if I select a task that has run successfully, the memory total still increases, but by a much smaller amount. Agan selecting the failed task bumps the increment back up to its previous level of 2-4GB per refresh. While composing this post I have watched the memory usage of the IE process increase by over 400MB.

Has anyone else noticed this? I have not upgraded the QVS to SR2 yet - is this addressed in that version?

Scott Moon

14 Replies
markmccoid
Partner - Creator II
Partner - Creator II

Since we are talking about memory leaks in QV. I am running QV9 SR5 on a server with 16 gig of RAM and everything works fine until I have multiple people start adding new report objects via the IE Plugin.

We are working with a QV file that is only 10Meg in size and when I have about 7 people making changes my QVS memory usage goes up to 16 gig and I have to kill the process.

Has anyone else experienced this?

Mark

StefanBackstrand
Partner - Specialist
Partner - Specialist

Hey,

Again, this sounds like some kind of record in memory usage. 😉

No seriously, I would say that sounds extremely rare - and that it most probably comes from the fact that the objects users create are extremely large/complex, that the data model is badly designed or that we have a bug. The latter seems less plausible though, since a bug with that high impact/visibility would have showed itself earlier, and hence probably is specific to your environment. Which brings us back to objects and data models.

1. What type of objects do users create?

2. Does the document have any synthetic keys in its data model? Se the table view.

pablolabbe
Luminary Alumni
Luminary Alumni

My customer is running SR6 and the problem is still present when QEMC is left opened in the status>task sheet. I have monitored the memory consumption. In my case around 300k on each automatica refresh every 5 seconds. I identified the problem when iexplore was consuming 1GB of RAM in a user session. Closing iexplore memory was dropped. Customer running Qlikview server 64x 9 SR6 build 9.0.7646.9. on Windows 2008 R2 Standard Edition.
schlettig
Partner - Creator
Partner - Creator

Hi,

same here at two customers running QV9SR6 Enterprise on a 2003 Server.

Mozilla Firefox however has no recordable leak though.

That is to say it at least, annoying at customers' allowing only IE.

Regards,

Christian

StefanBackstrand
Partner - Specialist
Partner - Specialist

The memory leak in QEMC (IE) is being looked at in the v11 track, and an eventual fix for it will be in that version, if a good solution is found. If that is ported to v9 and/or v10, we cannot answer at the moment, since it depends on the fix.

I've had some discussions with R&D about this and apparently it's been difficult to fix this specific issue in IE.

That is the information we've got at the moment.

Note: I believe that a workaround is to uncheck the "Automatic refresh" in the task overview.