Jobprocessor Delegate Host RAM usage, release of InventorObject

[jan.wagnerRB67Z]

Hi all,

In Vault Professional 2025 I created a custom job to modify properties using IExplorerUtil.
I noticed that after ~200 parts and assemblies updated, the RAM usage exceed 5GB. It seems that when executing many custom jobs in sequence, the InventorObecjt object of IJobProcessorServices is not released.

Is there an option to do this manually?

Vault API says that "This object should be initialized and released by framework. Extension developer doesn't need to take care of that." But apparently that seems not to be the case.

                ACET.IExplorerUtil explorerUtil = ACET.ExplorerLoader.LoadExplorerUtil(connection.Server, connection.Vault, connection.UserID, connection.Ticket);
                ACW.File vltFile = webServiceManager.DocumentService.GetLatestFileByMasterId(fileMasterId);
                explorerUtil.UpdateFileProperties(vltFile, properties);

I currently stop and restart the Jobprocessor.exe every five minutes to prevent it from crashing.

Many Thanks,

Jan

[jan.wagnerRB67Z]

Hi all,

In Vault Professional 2025 I created a custom job to modify properties using IExplorerUtil.
I noticed that after ~200 parts and assemblies updated, the RAM usage exceed 5GB. It seems that when executing many custom jobs in sequence, the InventorObecjt object of IJobProcessorServices is not released.

Is there an option to do this manually?

Vault API says that "This object should be initialized and released by framework. Extension developer doesn't need to take care of that." But apparently that seems not to be the case.

                ACET.IExplorerUtil explorerUtil = ACET.ExplorerLoader.LoadExplorerUtil(connection.Server, connection.Vault, connection.UserID, connection.Ticket);
                ACW.File vltFile = webServiceManager.DocumentService.GetLatestFileByMasterId(fileMasterId);
                explorerUtil.UpdateFileProperties(vltFile, properties);

I currently stop and restart the Jobprocessor.exe every five minutes to prevent it from crashing.

Many Thanks,

Jan

[johannes.bauer]

I suggest creating those posts in the Customization forum. Or create an ADN Case. Thanks

[jan.wagnerRB67Z]

Hey @johannes.bauer ,

i just did that. Feel free to delete this post.

[Markus.Koechl]

Hi @jan.wagnerRB67Z, this is a known issue currently under investigation. However, the release of the InventorServerObject works in general. The issue relates to the use of IExplorerUtil, a wrapper that provides access to the Vault Client commands.

[ihayesjr]

You could try to changing the restart setting for the Job Processor.

Vault Help | Configure Job Processor Use Limits for CAD Services | Autodesk 

[jan.wagnerRB67Z]

@ihayesjr 
We have them on 1/10 of the default value. Unfortunately they do not apply in this case.

[JelteDeJong]

@Markus.Koechl 

If the IExplorerUtil is a wrapper. Can i then conclude that if we would use the standard api (not the wrapper) that it would solve the issue?

[Markus.Koechl]

Hi @JelteDeJong. Yes, following the theory. At least, you get options to debug in depth. I am about to provide coding samples and kindly ask for patience while I finalize validation.