License Server Seems to Have a Memory Leak

[vlado]

This should have been corrected for the service pack (vrlservice uses a lot less memory now).

Best regards,
Vlado

[dbuchhofer]

running into this now

this is what i walked into this morning

[dbuchhofer]

More details.. I am set up as the primary target for the render farm to snag a license from. my coworker has borrowed my dongle for the evening, and unthinkingly (I reminded him several times) sent a job to the farm.

I've had this happen many times previously, much more frequently in the past several weeks however. all previous times it has been with the Dongle in the computer.

[jreynolds]

Hi, and sorry it's so late... for whatever reasons I missed a notification that there were replies to this thread.

Dieter, there aren't any immediate plans to connect Flood with VRay with our current resources being focused on rewriting flood. Check your PM though.

Vlado/ Dave, I have had much more luck with VRL server since the SP1 upgrade. I believe it has only gone down once, perceived from my end, and this was probably due to IT reconfig or something like that.

I think the trick is to make sure everything gets the SP1 upgrade.

--Jon

[paulison]

this is what i walked into this morning

yeah thats exactly what i've got. over 1.3 GB memory usage at times. normally it sits on about 4Mb but everything now and then something goes wrong.

I have the manager and rendering machines on this network with my workstation which has the dongle. The other machines refer back to the workstation for the licence. the workstation is also connected via VPN to the office so it may grab the occasional texture from there at times when a job is sent to render. Could this be the cause?

When the problem occurs, Max starts running very slowly and eventually crashes. I',m not sure whats starting the problem but think it may be when i click to network render....it can sit there for a long time before the dialogue shows up.

This is a relatively clean installation and i havnt had any problems other than with quicktime (who doesnt have problems with this POS)

The only other thing i can think of is that when i uninstalled the previous version, there was an error and i noticed today that there was already a vrlservice running which may well be the old version, so that probably didnt uninstally properly. I guess i'll try that first

[pixelstudio]

are you sure the license server isn't having a conflict with a firewall/virus scanner ? if have some serious problem when i tried avg

[dbuchhofer]

I've definitely got no workstation based firewall on mine.

Occasionally after the above errors, when i attept to restart the vrlservice executable it will ask me to insert my wibu-box #######. at which point i have to remove the dongle and reattach it.

My personal workstation is the only one that is experiencing this issue, as it is the primary license server for the renderfarm (a farm of 12 machines) it appears to coincide definitely with a net render job.

I'd also like to say that I've been using the dongle since siggraph of 2006 and only started having issues recently. they may (but I'm unsure) coincide with when I had installed max2008 on this workstation. also around the same time i installed the SP1 version of vray on my machine.

[dbuchhofer]

To add more info:

Starting the vrlservice.exe begins at 6mb of ram use. every roughly 20 seconds it allocates an additional 2008KB-2036KB of ram. This is with 0 network renders running currently, so my above guess about it being related to licence requests seems to be false.

Edit1: Removing my dongle from the workstation causes the same above behavior.
Edit2: Trading dongles with a coworker has the same behavior.
Edit3: Removing myself from the network completely, and the vrlservice shows the same behavior. I only watched it grow until 60mb.. but from what you say above, thats already something very wrong

[vlado]

If you upgrade to the latest WIBU drivers from http://wibu.com/download_user.php?lang=en does the issue still persist?

Best regards,
Vlado

[dbuchhofer]

It appears so far that it HAS fixed it.

[jreynolds]

We've been having great luck with the VRL server for the longest time and then had a crash last night.

The only thing I can come up with that might have caused this is that I've been making a few template scenes for our RnD dept and a scene was sent with both mult-pass moblur and as tasks in chunks of 5 frames each. Is there a chance that every time VRay renders a new moblur pass and/ or when it doesn't release the renderer for each frame the VRLserver is building up memory?

I should also note that there were a variety of maybe 4 other VRay jobs on the farm which were submitted in the same method we have been for the most part, no multi-pass and one frame per task.

Best regards,
--Jon

[vlado]

Some people seemed to have problems with memory usage which went away after updating the WIBU key drivers from http://wibu.com/download_user.php?lang=en

Not sure if this is the same problem though.

Best regards,
Vlado

[jreynolds]

We did a reinstall of the WIBU key driver and it had the same version number that we had before so I think we were all up to date when the crash happened. I'm hoping that the differences I noticed in the job that was submitted last night will help us not to crash it again but if you think of anything else it would be great to hear

Best regards,
--Jon

[dbuchhofer]

Wanted to update on mine.. I've peeked at it occasionally, and it hasn't crashed on me since updating the wibu drivers, but the vrlservice is using 45mb now, and I've seen it up to 120 on occasion also. I've pretty much just ignored it, but it still seems on the high side for what it is

[jreynolds]

Do you find that memory usage is higher when submitting jobs with multi-pass moblur or jobs that have multiple frames for one task?

Thanks,
--Jon