vue-leaflet/Vue2Leaflet

large CPU and Memory usage on open Vue devtool window

Open

#404 建立於 2019年6月13日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)JavaScript (1,942 star) (380 fork)batch import
confirmedhelp wanted

描述

My application uses a web socket to update markers and show transport . When I open devtool, I see a huge amount of events [ready $emit by LGeoJson] Chrome uses 2GB, the CPU goes to a zone above 60% On my map about 20 static LGeoJson and 100 static event markers are displayed. Even with such a small number of objects, I get crash vue devtool.

If I go to tab "Events" and push "clear" events, the memory is released, there is no load CPU and no crush devtool.

Next, I add transport objects whose coordinates change dynamically on a web socket and see events [update: latLng $emit by LMarker] There are a lot of them and it is very difficult to track down the desired event.

I understand that the problem is most likely in dev tools, but is it possible to disable map objects from $emit?

Browsers Affected

  • Chrome 75.0.3770.80 vue devtool 5.1.0

Versions

Leaflet: v1.5.1
Vue: v2.6.7
Vue2Leaflet: v2.1.1

貢獻者指南

技術棧
javascriptvue
領域
frontendperformance
議題類型
performance
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Vue.jsLeafletEvent handling
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Investigate the Vue2Leaflet source code, specifically the LGeoJson and LMarker components, to understand how events are emitted. Look for any existing option to suppress events or consider adding a prop like 'disable events'. Review the Vue Devtools documentation for event filtering. The issue reporter suggests disabling $emit on map objects; this could be achieved by adding a conditional emit guard.