ID 383339 - Deleting the catalog item for a cancelled interactive render does not free its memory

Problem summary:

When deleting a Catalog item, it is expected that its image buffers are immediately released, and associated memory freed. If a preview render is cancelled then the memory is not freed. This will eventually lead to out-of-memory issues.

Steps to reproduce:

1. Launch Katana and load the attached scene.
2. Open a live view of Katana's memory usage.
3. Note the amount of memory Katana is using.
4. Start and cancel several preview renders.
5. Note the amount of memory Katana is using.
6. Delete the Catalog items for each of the cancelled renders.
7. Note the amount of memory Katana is using.

Expected behaviour:

The amount of memory that Katana is using should decrease as each cancelled Catalog item is deleted.

Actual behaviour:

The amount of memory that Katana is using does not decrease and eventually out-of-memory errors occur.

Workaround:

Do not cancel preview renders. Performing preview rendering with the only the primary AOV and keeping resolutions low will help to delay the onset of out-of-memory conditions, but doesn't prevent them.

Reproduced by support

This bug has been reproduced in:

• 3.6v4 - Windows 10
• 3.6v1 - Windows 10
• 3.5v4 - Windows 10
• 3.5v1 - Windows 10
• 3.0v9 - Windows 10
• 3.0v1 - Windows 10
• 2.6v4 - Windows 10
• 2.5v2 - Windows 10

Earliest version tested
Katana 1.6v3
- This issue appears to be in all versions of the product