homebridge-camera-ui: Memory leak

accidentally I get some times after Motion ON memory leak, this was happened in 5.x.x beta and release:

OS: Raspbian GNU/Linux Bullseye (11) Node: v16.3.1 Hardware: RPI 4B

[12.01.2022, 07:44:27] [CameraUI] Tył: Motion ON
(node:9259) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 closed listeners added to [HAPConnection]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
[12.01.2022, 07:44:42] [CameraUI] Tył: Motion handler timeout.
[12.01.2022, 07:44:47] [CameraUI] Tył: Closing recording process

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 19 (19 by maintainers)

Most upvoted comments

So, after 12h test No any memory leak, looks like the problem is solved and can be closed.

grzegorz914 on Jan 13, 2022

no, looks like all ok but continue testing.

grzegorz914 on Jan 13, 2022

OK, may be print log with:

Starting video stream: native

all other parameter are irrelevant.

done in v5.0.5-beta.10

seydx on Jan 13, 2022

OK, may be print log with:

Starting video stream: native

all other parameter are irrelevant.

grzegorz914 on Jan 13, 2022

again some error:

[13.01.2022, 07:48:51] [CameraUI] GET /files/Prz%C3%B3d-241d97da2f-1642055942_c_CUI.mp4 206 40.866 ms - 7202828
Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:98:16)
[13.01.2022, 07:48:51] [CameraUI] GET /api/recordings?page=4 200 4.714 ms - 1395
[13.01.2022, 07:48:52] [CameraUI] GET /files/Prz%C3%B3d-241d97da2f-1642055942_c_CUI.mp4 206 4.745 ms - 6875148
Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:98:16)
[13.01.2022, 07:48:53] [CameraUI] GET /api/settings/general 304 5.110 ms - -
[13.01.2022, 07:48:53] [CameraUI] GET /files/Ty%C5%82-106e6be348-1642014617_c_CUI@2.jpeg 200 12.876 ms - 84779
[13.01.2022, 07:48:53] [CameraUI] GET /files/Ty%C5%82-fcd2b31583-1642014324_c_CUI@2.jpeg 200 2.680 ms - 85140
[13.01.2022, 07:48:53] [CameraUI] GET /files/Ty%C5%82-d7450e487f-1642014110_c_CUI@2.jpeg 200 2.711 ms - 86487
[13.01.2022, 07:48:53] [CameraUI] GET /files/Prz%C3%B3d-241d97da2f-1642055942_c_CUI.mp4 206 14.600 ms - 6481932
Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:98:16)
[13.01.2022, 07:48:53] [CameraUI] GET /files/Ty%C5%82-e8f174ebb2-1642013411_c_CUI@2.jpeg 200 3.824 ms - 85445
[13.01.2022, 07:48:53] [CameraUI] GET /files/Ty%C5%82-1bec459342-1642012953_c_CUI@2.jpeg 200 3.563 ms - 85701
[13.01.2022, 07:48:54] [CameraUI] GET /files/Prz%C3%B3d-241d97da2f-1642055942_c_CUI.mp4 206 6.026 ms - 6154252
Error: write EPIPE
    at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:98:16)
[13.01.2022, 07:48:55] [CameraUI] GET /files/Prz%C3%B3d-241d97da2f-1642055942_c_CUI.mp4 206 14.382 ms - 5761036

no thats already fixed in v5.0.5-beta.9, edited my post above

seydx on Jan 13, 2022

@grzegorz914

~v5.0.5-beta.8 online~ v5.0.5-beta.9 online

sudo npm i -g homebridge-camera-ui@5.0.5-beta.9

seydx on Jan 13, 2022

And what is this all not rewriting:

Thats from the internal history api, only shown if debug is enabled

seydx on Jan 13, 2022

I will do but need some time to test this because memory leak not always happens.

grzegorz914 on Jan 12, 2022