topic Allocated Memory Exceeded - QV11 in QlikView

Allocated Memory Exceeded - QV11

Anonymous — Mon, 26 Jan 2026 18:19:17 GMT

I see a ton of questions about this error for old versions of QlikView (mainly 8.5) but I'm running QlikView 11, and running into it in a situation that should not be causing problems. It's happening on two different servers. Here's the setup:

* Running QlikView 11 IR on both servers

* One server is brand new, has a ridiculous number of CPU cores and tons of RAM (40 and 128GB, IIRC) and is not running anything but QlikView. The other is our in-house test server which I believe is somewhat less capable (I don't know the exact specs).

* Working Set is set to 70% low, 90% high

* The object where I've found this problem is a simple table box within a container.

- The container has only 5 objects in it

- The table box is showing 8 fields, and there are only 2,432 lines

- The table that's in the "middle" of the fields being shown contains 2 of the fields. 4 fields are one table away, 2 fields are 2 tables away.

* The error occurs in the Ajax client

* The "Allocated Memory Exceeded" error is seen after clicking in the table box to make a selection.

Any suggestions?

Thanks,

Kent

Allocated Memory Exceeded - QV11

pover — Fri, 06 Jan 2012 01:00:08 GMT

Kent,

I've seen some buggy things in QV 11 concerning containers. I've repeatedly had fatal errors that force me to close QV because of them. I've been given the allocated memory exceeded when using alternate states and dimension limits so I don't know what's going on, but there are still numerous errors in QV11. Does the table box show alright without it being in a container?

I would report it as a bug to make sure it gets fixed in a future release.

Karl

Allocated Memory Exceeded - QV11

Anonymous — Tue, 10 Jan 2012 21:43:06 GMT

I've been banging on this some today, and here's what I've found:

1) It will sometimes manifest itself the first time a selection is made after switching to the sheet containing the container with the table boxes in it. After the first occurrence, it doesn't throw an error again until several more selections have been made - For example, I'll make a random selection, clear it, make another, etc. until 7-11 selections have been made and cleared before I'll see it again.

2) A straight table containing the same data as the table box does not appear to have this issue - 40-50 selections made and cleared and I never saw it.

3) When I pulled the table box out of the container, around 35 selections made and cleared and I never saw it - But the table box still in the container started acting up.

So, it appears that the table box inside a container is the common denominator.

Allocated Memory Exceeded - QV11

Alexander_Thor — Wed, 11 Jan 2012 15:35:16 GMT

Dear flyingcheesehead,

Please report it to support so they can debug it.

Seen some strangeness with containers aswell but have not been able to track it down.

Off-Topic: Your working set could probably be tweaked if you like. Right now you have 12.8gb of RAM allocated for your OS which sounds a bit big.

More off-topic: "Best handle on QlikCommunity"-award has found a winner! Love it!

Allocated Memory Exceeded - QV11

Anonymous — Tue, 17 Jan 2012 23:03:15 GMT

The bug has been reported, and it sounds like it'll be fixed in SR1.

Allocated Memory Exceeded - QV11

Mon, 16 Apr 2012 10:07:28 GMT

Just installed QV11 SR1 and still getting the same errors when using Dimension Limits within a container

Allocated Memory Exceeded - QV11

alfredlee — Thu, 19 Apr 2012 01:18:12 GMT

same here.

Allocated Memory Exceeded - QV11

Anonymous — Mon, 30 Apr 2012 16:09:50 GMT

Andrew11 and alfredlee,

Please report it as a bug again - The original bug (Bug ID 44683) was fixed in SR1, so as far as QlikTech is concerned, it's fixed. It also is working properly now in all the documents that I submitted to them with the original bug report, so it may either be a different bug or maybe they didn't completely fix the bug. Either way, that bug ID is in the release notes as "fixed" so QlikTech thinks it's fixed.

Re: Allocated Memory Exceeded - QV11

Wed, 02 May 2012 05:38:28 GMT

Dimension limits do not work on tables that contain mini charts.

Allocated Memory Exceeded - QV11

Sun, 27 May 2012 11:03:21 GMT

facing the same when using the expression in dimensions. Any suggestion or work around ?

Re: Allocated Memory Exceeded - QV11

Thu, 26 Jul 2012 16:40:26 GMT

I am still getting this bug in QV 11 SR1. I will report it myself if someone else has not yet.

Re: Allocated Memory Exceeded - QV11

Anonymous — Thu, 04 Oct 2012 03:05:14 GMT

It looks like QlikTech has fixed some additional problems like this in QV11 SR2. Specifically, bug ID 46255: "Qlikview Desktop - Allocated memory exceeded with Count (Distinct) in the expression." That also hints at a workaround for those of you not planning on upgrading to SR2. Were those of you who were still having problems in SR1 using a count(distinct) in the expression?

Also, bug ID 46892: "Allocated memory exceeded" when creating a Block Chart with 3 dimensions.

I'm curious to see if anyone will have Allocated Memory Exceeded errors in QV11 SR2...

Re: Allocated Memory Exceeded - QV11

simondachstr — Wed, 12 Dec 2012 20:21:11 GMT

I have the same error popping up. In my case I am using a Pivot Table with 34 dimensions, all of them displayed only upon a certain condition.

It works without any problems when I'm developing it, however it's differently when the document is opened on the WebServer.

A remarkable observation is that the error is non-reproducable. Sometimes it stops calculating, other times it works fine with the same selections made.

Re: Allocated Memory Exceeded - QV11

kamakshisuram — Wed, 19 Nov 2014 06:43:00 GMT

I got this error when I used 3rd dimension as Calculated Dimension. Then I removed Calculated and made it to Normal dimension which worked fine.

Re: Allocated Memory Exceeded - QV11

Thu, 08 Jan 2015 15:57:06 GMT

I have seen this error also, but in this scenario: A container that has 2 straight tables in it. If I launch the qv app as a user that has column reduction, one of the tables will present the error but if I make a selection then data appears as expected and all seems fine, and if I de-select that same selection, data still appears as expected. Both charts have conditional statements that hide some columns for this user. But if I launch the same qv app as a user that has access to see all column, both charts appear with data and the error never occurs.

Re: Allocated Memory Exceeded - QV11

Tue, 02 Feb 2016 21:53:23 GMT

This issue does not appear to be fixed. I'm getting the same error in a bar chart.

I had two (expression) dimensions, and several expressions (only one shown at a time, controlled w/ conditions).

To troubleshoot, I started to disable expressions. I basically got it down to one dimension, one expression, still no luck. However, if I create a new expression which is identical to the one I have left, everything works perfectly. This is definitely a bug. I am tired of putting bandaid's on this issue. Can anyone help shed some light on why this is happening?

Re: Allocated Memory Exceeded - QV11

Anonymous — Tue, 02 Feb 2016 22:53:39 GMT

Albert, when you say "(expression) dimensions" do you mean calculated dimensions?

If so, if there is any way at all that you can do what you want to do without using calculated dimensions, that will help immensely with both RAM usage and the speed and responsiveness of your app. I would imagine that it will correct the Allocated Memory Exceeded issue too.

FWIW, I have not seen this issue again in a LONG time, so it may well be that it really is running out of memory.

Re: Allocated Memory Exceeded - QV11

Anonymous — Wed, 03 Feb 2016 18:06:42 GMT

We have an ongoing issue with QVS.EXE consuming all the memory too. Ticket raised with Qlik.

The latest suggestion they have is there may be a corrupt object in the qvw. This seems to tie in with what Albert Flecha reported in that he could recreate the expression form scratch and it worked fine. Corrupt objects can sometimes be accompanied by an entry in the server Event log, in our case we only once had this error but the memory leak happened frequently.

Look for article number 000002846 "Troubleshooting Exception Warnings" in the Support Portal for a guide on how to purge corrupt objects from your QVW. Which may help you here.

We have just cleared our application of any corrupt objects and are observing the results.

We also find that the high memory usage is intermittent and difficult to reproduce so only time will tell if purging corrupt objects has solved the problem.

Re: Allocated Memory Exceeded - QV11

Wed, 03 Feb 2016 18:45:53 GMT

Yes, that is what I meant. I need to use the calculated dimensions here because we have made our charts extremely interactive and flexible. An example of this is we provide a central navigation pane for our users to determine the way to set the date dimension across all the charts (Month, Week, Year). We also use tables & variables to change/update charts dynamically.

Re: Allocated Memory Exceeded - QV11

pover — Fri, 05 Feb 2016 07:46:00 GMT

Hi Albert,

Just curious. Why do you use a calculated dimension instead of multiple field dimensions with conditional show expressions? Is it to lower the maintenance cost of the charts?

Also, I'm not sure what you mean when you say

"I basically got it down to one dimension, one expression, still no luck. However, if I create a new expression which is identical to the one I have left, everything works perfectly"

Can you explain a little bit more what you mean?

Karl