Troubleshooting

Error in code snippets

CodeSnippetErrors

1st try

  • Execute "Execute Quick-Fix" on the errors

2nd try

  • Delete the hidden ".asdropins" folder

  • Restart UP

Prevent high memory consumption

It can happen that UPstudio is no longer operable. A common cause is a lack of reserves in the heap memory. This can be checked with the following setting:

grafik-20240918-134505.png

This displays the current utilisation of the heap memory in the footer of UPstudio:

If this is the case, the memory footprint can be reduced by reducing the resource dependencies. However, this reduces the memory requirement, which means that changes in the model require longer validation in the background. It is therefore a trade-off, although validation in the background does not normally cause any restrictions.

 

There are three possible settings:

  • Default: (highest memory requirements, most efficient validation in case of model changes)

  • Aggregated (medium memory requirements, less efficient validation in case of model changes)

  • Root (greatly reduced memory requirements, extensive validation in case of model changes)

 

Reduce generation time by hiding irrelevant folders

UP scans the destination folder before generating. Since for example Automation Studio creates several thousand files during compilation and stores them in different folders, the start of generation is delayed because these files must first be scanned.

For better generation performance: UP generates a ".actifsourceFileIdIgnore" file at Binaries, Diagnosis and Temp folder, with that file, scanning is disabled for that folder.

For other folders with same issue, exclude it with Eclipse filter settings:

Excluding the corresponding folders will speed up the scanning process.