Crash cause of (supposedly) opened file count. Solaris USD

   98   1   0
User Avatar
Member
2 posts
Joined: Nov. 2017
Offline
Hello!
At my current workplace I coordinate efforts to move into usd. Artists started to encounter errors which I'm attaching as a collage of screenshots. It all leads to a fatal crash eventually.

1. Hou loosing icons
2. Hou cannot access svg icons cache
3. Hou cannot access UI elements or DLLs
4. Hou failing to save session down

Essenstially it complains about to many files being open. What all affected people (representing minority of studio) have in common is that they are looking at the same layout of assets: about 300 4K udims, couple thousand .tx bitmaps in total.
This is windows environment, and we read from server. We do not get close to 100GB of RAM.
To repro the error you have to launch Karma viewport render, wait for it to finish, start clicking at UI elements and wait for it to happen. First symptom is missing icons.

Best lead so far is that we are leaking handles, although we are not actually increasing their number indefinately. We reach 130K of them, including 120K being empty semaphores. Number of open files peaks at around 3.3K.

There is plenty of sussy things in this story but were you would recommend me to start sniffing? Creatively speaking, those pixels render just as intended.

Corrupted .tx'es? Karma waiting to long for network? Starts tracing righ away yet does it very slow while I suck 4Gbps for the first 10 seconds and 1Gbps for the remaining first render attempt since sesion start.

AI tells me that this amount of handles is abnormal, is it really? I could go down the path of optimizing udim count and .tx params like tile size, but hey, we wanna do big things too, I thought USD was made for it.

Any input appreciated!

Attachments:
67936a6a-6513-431c-8101-8bad3ea29e90.png (761.9 KB)

User Avatar
Staff
648 posts
Joined: Aug. 2019
Online
One thing you can do is run Process Informer: https://systeminformer.sourceforge.io/downloads [systeminformer.sourceforge.io]

Install and run it, then reproduce your issue in Houdini.

Once you start getting the "Too many open files" message, find Houdini in Process Informer, right click on it and choose Properties, then go to the Handles tab. Scroll down to where the Type column is File. This should show you all of the file handles that are currently open.
  • Quick Links