invoso.com Report post Posted 08/14/2018 08:31 AM HI, we see vgIvrService.exe *32 occupy memory after whole day up to 1 Gb After restart memory usage is about 200 Kb. Our main suspect is VBS module we use. we use: set vg = CreateObject("vgServices.CommandLink") vg.Play_Stop $RV_LINEID vg.Play_Start $RV_LINEID, "$RV[MusicOnWait]" vg.Run_ResultReturn $RV_LINEID, "success" set vg = Nothing to start play Music on hold next is empty play module to set on {timeout $RV[_waiting_loop_interval]} goto [STOP MoW wait line customizable] to customize waiting time independent from music length. next VBS set vg = CreateObject("vgServices.CommandLink") vg.Play_Stop $RV_LINEID vg.Run_ResultReturn $RV_LINEID, "success" set vg = Nothing Have You any idea how to make MoH with length parameter? (MoH defined with play time as variable) Or how to decrease memory occupying? Share this post Link to post
invoso.com Report post Posted 08/14/2018 08:58 AM Memory usage not decreasing even after finishing all connections. test server use 50 channels for incoming calls and is occupied 6 hours per day. Share this post Link to post
SupportTeam Report post Posted 08/14/2018 10:31 AM Memory usage will depend on what actions the scripts take, and 1GB is not unusually high for a 50 channel system. VoiceGuide is a .NET based application, and .NET framework takes care of memory reservations, so VoiceGuide does not manage the memory allocations directly. The VBScripts quoted would not cause any permanent memory leaks. Recommend tracking memory usage of the process over a week or so and you will most likely see that memory fluctuates up and down within a range. This tool may be useful here: https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer Share this post Link to post
invoso.com Report post Posted 08/14/2018 11:08 AM I solved problem using "do not wait for VB script to complete" Share this post Link to post
SupportTeam Report post Posted 08/14/2018 11:22 AM The "do not wait for VB script to complete" option does not affect how the VBScript is ran and the memory used by the process that runs the script. The script is still ran the same way. It's just that VoiceGuide does not pause until the VBScript completes. Share this post Link to post
invoso.com Report post Posted 08/14/2018 11:59 AM in temp folder I have 17 000 vbs files ... with 50 active calls (each come back to MoH VB Script start and stop modules every 30 seconds) Share this post Link to post
SupportTeam Report post Posted 08/14/2018 08:35 PM Can you please open a Windows' Command Prompt, then go to the VoiceGuide's \temp\ subdirectory and then run this command: dir > dir.txt please post the created dir.txt file here. (maybe .ZIP it up first beforehand). We can then see the names of all the files in the \temp\ subdirectory and comment. Share this post Link to post
invoso.com Report post Posted 08/17/2018 08:59 AM as You wish vbs_list.zip Share this post Link to post
SupportTeam Report post Posted 08/17/2018 10:08 AM The reason why there are so many files in /temp/ subdirectory is because the VoiceGuide scripts used on this system call the 'Run VBScript' module hundreds of times (many lines show 800+ times) during many of the calls. The second digit in the temp vbs filename is the counter of how many times the "Run VBscript" module was ran during current call. Share this post Link to post