@newleaf Adding an update here. Upon repeated testing, it was discovered that the issue described above happens after about 16348 still image captures (individual camera capture invocations). After that time, the camera becomes unresponsive until after a reboot.
Being that this number is close to 2^14 (16384), is there a register or counter that is overflowing/wrapping? Perhaps a bug in the driver or camera firmware?
After speaking with out of our engineers, he noted that that the NULL pointer dereference at virtual address 00000000 could simply be the side effect of an internal issue.
We will be exploring an upgrade to JetPack 5 and continue testing.
Thank you!