Closed deanlee closed 4 months ago
VipcClient::recv and vipcClient::connect have similar problems, e.g. vipcClient:connect will returns true even if an attempt is made to connect to a non-existent stream type.considering use another pr to fix these issues.
@adeebshihadeh : In addition, vipc currently only uses yuv type buffs, and rgb seems to have been deprecated. Can this part of the code be deleted? This can make vipc's code much cleaner.
Doesn't the map still use it?
the map_render creates vipc buffer as yuv. Looks like a bug, though it probably doesn't actually affect the result. https://github.com/commaai/openpilot/blob/5f045176775c8c2cdd7f85e7229f78cf26f0c013/selfdrive/navd/map_renderer.cc#L92
closed , moved to https://github.com/commaai/msgq/pull/624
the vipc client still can connect to the ipc path even if the camerad is not running. This could be due to the camerad not shutting down properly and the ipc path not being removed.
ipc_sendrecv_with_fds
will returns -1 In this case. this causes the following assertion to fail.This bug can be reproduced by clicking “preview driver camera" button quickly and continuously in the UI interface.