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
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.
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 
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
It appears so far that it HAS fixed it.
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
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
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
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
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
While checking on the license server today I noticed that the VRLserver service was using about 140 MB and peaked around 180 MB which was really odd because there was nothing on the farm and I was the only person I could find who had used it all day. After restarting the service it returned to under 5 MB.
Do you have any suggestions to what might help us not have to worry so ?
Best regards,
--Jon
Are you running the 64-bit version of the license server? If not, you can try it - if nothing else, at least Windows will give it more memory if necessary. I am looking at what might be causing this; it may not be memory consumption as such, but a memory fragmentation issue.
Best regards,
Vlado
No all of our license servers are 32-bit. Thanks for taking a look into what the problem might be. Let me know if you haven’t been able to reliably reproduce this and I can see if our IT dept can do some sort tracking.
Thanks,
--Jon
just thought i’d add that i’d seen this for the first time recently - after constantly running for something like 200+ days with no errors at all we started seeing buckets slightly mis aligned, then the water mark appear - we reset the license server and noticed that it was on about 250mg of ram.
All fine now though after restarting…
well I just started using latest vray and I noticed same thing happening. Though it does not happen all the time, often I will start a job and it will be at 2.85 gb (x64) by the time it does frame 20 its already at 3.0gb and through the night it will be over that.
Are you sure this is because of the license server specifically?
Best regards,
Vlado
no not absolutly sure. Its a very complex scene, an object is getting closer to camera, this could also be why. More tests needed