Closed HERO-YDX closed 4 months ago
Thanks for the detailed issue!
I'm familiar with that error "Critical error during the static RTTI initialization", it has also happened to us. However, we are not sure either of what causes the error, seems to be some sort of race condition as it happens seemingly at random. We just implemented a workaround that just re-launches the renders that fail, and for now it has worked without more issues (hopefully in your case it does not give you any issues either)
If I have more time I can look into it, it only happens under confocal
or exhaustive
scenes, and not in single
(i.e. scenes with only one laser point). The confocal
and exhaustive
scenes call Mitsuba 3 multiple times, so it might be some cleanup that needs to be done between renders.
In any case, if this issue gives you more problems, or you happen to find more info, please reach back to us.
Thank you. I will try it. Have a great day and thanks for your support!
Issue Description
Thank you for this wonderful work. I encountered some issues.
When running the
confocal-scene
example, the program does not get interrupted but encounters a "Critical error during the static RTTI initialization" (see the output below). This error occurs at different points during each run, and the class that cannot be located varies each time. The parameters used are "llvm_ad_rgb".I tried replacing different
obj
files in the experiments, and this issue occurs multiple times, especially when the rendering time is long.Additionally, the examples provided in
mitsuba3-transient-nlos
can run without issues.System Description
OS: Ubuntu 22.04 y-tal: 0.16.1 mitransient: 1.0.3 Mitsuba3 version: Manually compiled
I am using a manually compiled version of Mitsuba3. The available parameters are as follows:
Output
Please let me know if you need any additional details or modifications.