Embeddable has been destroyed error happened after interacting with the Embeddable

[angorayc]

Found an error Embeddable has been destroyed when rendering with LensEmbeddable

Screen.Recording.2022-08-02.at.16.53.58.mov

Steps to reproduce
In #137882 security solution > explore > hosts > all hosts
case 1:
update the global timerange
case 2:
brush on of the area charts to update the timerange

How to add data to security solution: (can run a local ES and skip step 3)
https://www.elastic.co/guide/en/beats/auditbeat/current/auditbeat-installation-configuration.html

example auditbeat.yml

# =========================== Modules configuration ============================
auditbeat.modules:

- module: file_integrity
  paths:
  - /bin
  - /usr/bin
  - /usr/local/bin
  - /sbin
  - /usr/sbin
  - /usr/local/sbin

- module: system
  datasets:
    - package # Installed, updated, and removed packages

  period: 2m # The frequency at which the datasets check for changes

- module: system
  datasets:
    - host    # General host information, e.g. uptime, IPs
    - process # Started and stopped processes

  # How often datasets send state updates with the
  # current state of the system (e.g. all currently
  # running processes, all open sockets).
  state.period: 12h

# ======================= Elasticsearch template setting =======================
setup.template.settings:
  index.number_of_shards: 1
  #index.codec: best_compression
  #_source.enabled: false

# ---------------------------- Elasticsearch Output ----------------------------
output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["localhost:9200"]

  # Protocol - either `http` (default) or `https`.
  # protocol: "https"

  # Authentication credentials - either API key or username/password.
  username: "{YOUR_USERNAME}"
  password: "{YOUR_PASSOWRD}"

[elasticmachine]

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

[flash1293]

Calling super.destroy in

kibana/x-pack/plugins/lens/public/embeddable/embeddable.tsx

Line 878 in 42d3966

super.destroy();

is triggering another render in some cases. To avoid this, this.isDestroyed should be set before calling super.destroy()