Crash sometime after calling RelevantStage.destroy() in omni.kit.widget.material_preview

Omniverse Developer
1

Modified the MaterialPreviewProducer slightly but RelevantStage is untouched. Create crashes a couple seconds after the destroy call has finished and returned. I’m guessing it is an event being triggered but have not been able to track it down. Here is the error messages

2021-09-17 22:26:43 [332,945ms] [Info] [carb.scenerenderer-iray.plugin] Shutdown with 0 unreleased Textures.
2021-09-17 22:26:43 [332,945ms] [Info] [carb.scenerenderer-iray.plugin] Shutdown with 0 unreleased Images.
... (Several other messages confirming the destroy fn has finished
2021-09-17 22:26:47 [337,101ms] [Fatal] [carb.crashreporter-breakpad.plugin] gpu.foundation.dll!carbOnPluginStartup
2021-09-17 22:26:47 [337,104ms] [Fatal] [carb.crashreporter-breakpad.plugin] rtx.scenedb.plugin.dll!+0x210bf
2021-09-17 22:26:47 [337,104ms] [Fatal] [carb.crashreporter-breakpad.plugin] rtx.scenedb.plugin.dll!+0x1fb2e
2021-09-17 22:26:47 [337,106ms] [Fatal] [carb.crashreporter-breakpad.plugin] carb.scenerenderer-rtx.plugin.dll!+0x394b6
2021-09-17 22:26:47 [337,106ms] [Fatal] [carb.crashreporter-breakpad.plugin] carb.scenerenderer-rtx.plugin.dll!carbOnPluginShutdown
2021-09-17 22:26:47 [337,108ms] [Fatal] [carb.crashreporter-breakpad.plugin] carb.scenerenderer-mux.plugin.dll!+0x73c5
2021-09-17 22:26:47 [337,110ms] [Fatal] [carb.crashreporter-breakpad.plugin] rtx.hydra.dll!+0x767db
2021-09-17 22:26:47 [337,110ms] [Fatal] [carb.crashreporter-breakpad.plugin] rtx.hydra.dll!+0x74d83
2021-09-17 22:26:47 [337,110ms] [Fatal] [carb.crashreporter-breakpad.plugin] omni.usd.dll!omni::usd::UsdContext::hasPendingEdit
2021-09-17 22:26:47 [337,110ms] [Fatal] [carb.crashreporter-breakpad.plugin] omni.usd.dll!omni::usd::UsdContext::SetBoundingBoxSemanticId
2021-09-17 22:26:47 [337,110ms] [Fatal] [carb.crashreporter-breakpad.plugin] omni.usd.dll!omni::usd::Layers::resolvePrimPathReferencesStatic
2021-09-17 22:26:47 [337,112ms] [Fatal] [carb.crashreporter-breakpad.plugin] carb.events.plugin.dll!+0x5c95
2021-09-17 22:26:47 [337,112ms] [Fatal] [carb.crashreporter-breakpad.plugin] carb.events.plugin.dll!+0x4ff2
2021-09-17 22:26:47 [337,113ms] [Fatal] [carb.crashreporter-breakpad.plugin] carb.events.plugin.dll!+0x66af
2021-09-17 22:26:47 [337,115ms] [Fatal] [carb.crashreporter-breakpad.plugin] omni.kit.loop-default.plugin.dll!+0x8dda
2021-09-17 22:26:47 [337,115ms] [Fatal] [carb.crashreporter-breakpad.plugin] omni.kit.loop-default.plugin.dll!+0x6fca
2021-09-17 22:26:47 [337,115ms] [Fatal] [carb.crashreporter-breakpad.plugin] omni.kit.loop-default.plugin.dll!+0x6d19
2021-09-17 22:26:47 [337,115ms] [Fatal] [carb.crashreporter-breakpad.plugin] ucrtbase.dll!configthreadlocale
2021-09-17 22:26:47 [337,115ms] [Fatal] [carb.crashreporter-breakpad.plugin] KERNEL32.DLL!BaseThreadInitThunk
2021-09-17 22:26:47 [337,115ms] [Fatal] [carb.crashreporter-breakpad.plugin] ntdll.dll!RtlUserThreadStart
2

Hi @Josh.n - I’m sorry we missed this…was this resolved in the latest update(s)? For help reporting and incl. relevant logs, please see: How to Report an issue with Omniverse - NVIDIA Omniverse Support

Cheers,
Edmar

P.S. We are constantly adding new tutorials and aggregate them all in the “learn” tab on the launcher (also see: https://developer.nvidia.com/nvidia-omniverse-tutorials).

he / him | LinkedIn | Discord ID: Prof E#2041
Omniverse: “A New Era of Collaboration and Simulation” (video)
Omniverse Create’s latest features show & tell: Twitch livestream.
As seen in VentureBeat | Physics Showcase

Omniverse Resources:
Open Beta | Documentation | Tech Requirements | Videos | Roadmap | Twitter | Discord | Twitch

PLEASE NOTE: If you are reporting a bug/issue, please provide OS, GPU, GPU Driver, the version of the app, and full log file (if applicable). For crashes, please zip and provide a link to your logs → C:\Users\ [YOUR NAME] \ .nvidia-omniverse\logs

3

I confirmed with Damien that they were experiencing the same issue. I am not sure if it has been fixed in more recent versions but the workaround was to just not destroy the second context.

4

Hello @Josh.n! I created an internal developer ticket about your issue. (For reference OM-42274)