NvDisplay Behavior upon Unexpected Termination of the Client Process#
When the client application or client process using NvDisplay unexpectedly terminates, the operating system automatically closes the file descriptor (FD) because the connection between client application/process and NvDisplay is via the FD. This triggers the FD close call to NvDisplay (DisplayRM). DisplayRM then cleans internal resources by freeing them. Next, it puts blank display output: the NvDisplay is still functional, but the output from NvDisplay is blank (black pixels). This is not the same as the NvDisplay safe state, because if the client application re-starts, it can still use NvDisplay to render valid display output.