topic Re: QVB.EXE memory problem in QlikView

QVB.EXE memory problem

Mon, 26 Nov 2012 10:16:16 GMT

Hi,

It seems like there's a max memory cap for QVB to function.

I'm reloading a QVW, QVB is used up to 18GB ram.

and nothing else get to run when this QVW is running from publisher.

Do you have the same problem?

or is this known already?

Thanks.

Re: QVB.EXE memory problem

Mon, 26 Nov 2012 10:19:37 GMT

and then, when this is going on too long, it drags QVS down.

So i ended up restarting all the services...

which is... not good.

Re: QVB.EXE memory problem

Thu, 07 Nov 2013 03:06:12 GMT

Hi Nick,

Were you able to find a solution to this, short of restarting the services?

Thanks,

Re: QVB.EXE memory problem

Thu, 07 Nov 2013 08:09:15 GMT

Hi DJ,

It's been quite some times, and i make a lot of changes now.

If i'm not wrong, i changed the way the qvw is being distributed.

I was using "Loop in field" on a field which i store all the users ID.

so when publisher runs, it will distribute to all these users, and i had a lot of users.

I used section access now.

What kind of problem are you facing?

From time to time, i still need to kill the QVB.exe and re-launch the task.

Re: QVB.EXE memory problem

Wed, 20 Nov 2013 18:02:53 GMT

We are having a similar issue where QVB.exe seems to have a memory leak and ends up consuming nearly all the 64GB memory on the server. Does anyone know the solution to fix this issue?

Thanks

Re: QVB.EXE memory problem

Mon, 25 Nov 2013 09:09:01 GMT

Hi,

If you see QVB.exe in the process, it probably means there's a task running in publisher.

it will disappear once the task is done. this is for my case.

sometimes, QVB uses up a lot of RAM for some reasons (usually bad issue), i will kill the exe, and re-launch the task.

or maybe optimising the script would help?

Re: QVB.EXE memory problem

Tue, 17 Dec 2013 01:06:34 GMT

I'm running into an issue where QVB isn't closing as its processes complete. So, we've got several instances of QVB just sitting there, taking up memory.

What's worse, we have several mission-critical loads running around the clock, so I can't just randomly kill off the QVBs, because they might be doing something.

Among other things, I need a method for tracing the individual running QVBs to the actual load, to see if it's legitimately active, or stalled.

Any ideas?

Thanks,
DJ

Re: QVB.EXE memory problem

Wed, 15 Jan 2014 14:16:18 GMT

Hi DJ,

No idea for the moment, but it'd be real useful if we have something like this.

I'm also hoping there will be some improvement in Qlikview.next for scheduling.

Good luck

Nick