core: Memory leak in hdmi_cec integration?

The problem

On a new / clean install of HA on a RasPi3b with default_config, sensors for monitoring and nothing (!) else activated with the exception of hdmi_cec via YAML free memory is constantly going down until system crashes. After removing it from the config system is stable (see graph below).

What is version of Home Assistant Core has the issue?

core-2021.1.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

hdmi_cec

Link to integration documentation on our website

https://www.home-assistant.io/integrations/hdmi_cec/

Example YAML snippet

hdmi_cec:
  devices:
    TV: 0.0.0.0
    Beam: 1.0.0.0
    AppleTV: 2.0.0.0
    PiHA: 3.0.0.0
    NSwitch: 4.0.0.0

Anything in the logs that might be useful for us?

CEC Scanner:

[11:00:18] INFO: Starting CEC client scan...
opening a connection to the CEC adapter...
requesting CEC bus information ...
CEC bus information
===================
device #0: TV
address:       0.0.0.0
active source: no
vendor:        Unknown
osd string:    TV
CEC version:   1.4
power status:  standby
language:      ???
device #1: Recorder 1
address:       3.0.0.0
active source: no
vendor:        Pulse Eight
osd string:    CECTester
CEC version:   1.4
power status:  on
language:      eng
device #4: Playback 1
address:       2.0.0.0
active source: no
vendor:        Unknown
osd string:    Wohnzimmer
CEC version:   unknown
power status:  standby
language:      ???
device #5: Audio
address:       1.0.0.0
active source: no
vendor:        Unknown
osd string:    Sonos Beam
CEC version:   1.4
power status:  standby
language:      ???
currently active source: unknown (-1)

Memory usage: grafik The jump marks the restart after disabling hdmi_cec in YAML config.

I am not sure if this is specific to my setup (i.E. is it only my TV that is messing it up), but I have tried to to isolate it as best as possible.

As this is a test machine I am happy to provide debugging info anytime…

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 20 (8 by maintainers)

Most upvoted comments

Sorry - that’s a bit above my head as I am not a developer.