Chromium behaviour on JetPack 5.0 DP

On the JetPack 5.0 Developer Preview, trying to launch Visual Studio Code yields no results unless the --no-sandbox. Even --disable-gpu appended doesn’t result in a launch.

Trying to launch a (non-snap) Chromium build too results in:

NvRmMemInitNvmap failed with No such file or directory
546: Memory Manager not supported

****NvRmMemInit failed**** error type: 196626

Error: Can't initialise nvrm channel

This is compounded with stack smashing errors, but those might be unrelated as they show up with --no-sandbox too.

1 Like

try snapless chromium
bash <( curl ) "scripts/"
this script will disable sandbox and use vulkan and install snapless chromium

For confirmation, you run the commands:
Error: Can't initialize nvrm channel - #4 by DaneLLL

And both commands show the error?

I can confirm that running with the sandbox disabled removes the issue.

However, that’s not a configuration that is palatable/safe to deploy for us. Will see what I can do on that front on the Chromium side…

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.