mirror of
https://git.libcamera.org/libcamera/libcamera.git
synced 2025-07-14 16:09:51 +03:00
53704ac3f4
The CameraManager class is not supposed to be instantiated multiple times, which led to a singleton implementation. This requires a global instance of the CameraManager, which is destroyed when the global destructors are executed. Relying on global instances causes issues with cleanup, as the order in which the global destructors are run can't be controlled. In particular, the Android camera HAL implementation ends up destroying the CameraHalManager after the CameraManager, which leads to use-after-free problems. To solve this, remove the CameraManager::instance() method and make the CameraManager class instantiable directly. Multiple instances are still not allowed, and this is enforced by storing the instance pointer internally to be checked when an instance is created. Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> Reviewed-by: Jacopo Mondi <jacopo@jmondi.org> |
||
|---|---|---|
| .. | ||
| camera | ||
| controls | ||
| ipa | ||
| ipc | ||
| libtest | ||
| log | ||
| media_device | ||
| pipeline | ||
| process | ||
| stream | ||
| v4l2_subdevice | ||
| v4l2_videodevice | ||
| camera-sensor.cpp | ||
| event-dispatcher.cpp | ||
| event-thread.cpp | ||
| event.cpp | ||
| geometry.cpp | ||
| list-cameras.cpp | ||
| meson.build | ||
| message.cpp | ||
| object-invoke.cpp | ||
| object.cpp | ||
| signal-threads.cpp | ||
| signal.cpp | ||
| threads.cpp | ||
| timer-thread.cpp | ||
| timer.cpp | ||