Yaffle/EventSource

EventSource causes IE11 to lock-up, freeze and act erratically with high-frequency EventSource in Angular 4

Open

#104 opened on 2018年2月8日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,873 stars) (320 forks)batch import
help wanted

説明

I'm using this EventSource polyfill in an Angular 4 application that calls an EventSource that returns new messages every 500ms. When using IE11 on Windows Server 2016, the IE window (and dev tools!) instantly lock-up and become unresponsive for a few seconds, before resuming but lagging the entire system, including Windows Task Manager. Curiously, Windows Task Manager reports no unusual CPU usage, or significantly increased memory usage.

I ran it with the IE F12 Developer Tools Profiler, which shows a lot of time is spent in Angular's zone handler and change-detection code - so something very inefficient is going on in there. I speculate this polyfill is conflicting with Angular's Zone.js patching of XMLHttpRequest.

Has anyone else observed similar behaviour?

コントリビューターガイド

技術スタック
javascript
領域
frontendperformance
Issue 種別
bug
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
unclear
前提条件
JavaScriptAngular basicsZone.jsIE11 debugging
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
25
調査方針
Investigate the interaction between the EventSource polyfill and Angular's Zone.js patching of XMLHttpRequest. Use IE11 F12 developer tools profiler to identify specific functions causing high time in change detection. Look into the polyfill's event source implementation in the repository to see how it handles high frequency events. Consider implementing a debounce or limiting update frequency to reduce Zone.js overhead.