Getting Fatal Error when zooming out on map on a Dashboard in Kibana

[jvernon214]

Receiving a Fatal Error when zooming out on the map or using Fit Data Bound. This happens when I am using the map on my dashboard. There is a screenshot attached to see the error.

Errors on the screen:

• Uncaught InvalidStateError: Failed to execute 'drawImage' on 'CanvasRenderingContext2D': The image argument is a canvas element with a width or height of 0. (https://fa47af10cc3745419ba22683aeacb14e.us-central1.gcp.cloud.es.io:9243/bundles/vendors.bundle.js:8)
• Version: 6.3.0
  Build: 17230
• Error: Uncaught InvalidStateError: Failed to execute 'drawImage' on 'CanvasRenderingContext2D': The image argument is a canvas element with a width or height of 0. (https://fa47af10cc3745419ba22683aeacb14e.us-central1.gcp.cloud.es.io:9243/bundles/vendors.bundle.js:8)
  at window.onerror (https://fa47af10cc3745419ba22683aeacb14e.us-central1.gcp.cloud.es.io:9243/bundles/commons.bundle.js:3:778104)

[jvernon214]

cc: @alexfrancoeur

[Kvrepo]

We are facing the same issue. Any update on this?

[alexfrancoeur]

@aaronjcaldwell @thomasneirynck @timroes any idea what might be causing this?

[timroes]

This error looks to me like maps are failing in case the element they want to draw in is 0 width or 0 height. The visualization infrastructure current doesn't (and never did) prevent a chart from drawing in a 0 width/height container. So if maps are having that issues when drawing into 0 width/height containers, they should check the element size before drawing into it.

We could think about making a safe guard against that into the visualization infrastructure, but this might be a larger change effecting all visualizations, so I want to carefully consider that. For actually fixing that issue, I would recommend, that maps will actually check their container before drawing into it, e.g. see the vislib implementation for an example: https://github.com/elastic/kibana/blob/master/src/ui/public/vis/vis_types/vislib_vis_type.js#L64:L66

@elastic/kibana-gis feel free to add me as a reviewer for that PR

[thomasneirynck]

thanks @timroes. This error comes from Leaflet (or maybe heatmap plugin, which is a 3rd party overlay). Leaflet manages the rendering of the canvas, so if we cannot detect the 0x0 size of the DOM-container before Leaflet does (and I don't think the visualization infrastructure currently allows this), we'll have to find another approach.

I think this might be a regression, or at least looks similar to #6343, as this was fixed once before. This might be because of upgrading to Leaflet 1.3 which introduces canvas-rendering (and likely the source of the drawImage calls for the tiles).

I will look into it, please stay tuned, thx

[jvernon214]

@thomasneirynck @timroes thanks for the update. I have an active cloud cluster of mine that does this, so if you need to test against a kibana instance let me know.

[thomasneirynck]

@jvernon214 that's great, thx, I'll ping you if I can't repro here on my end

[jvernon214]

cc: @kyreddie