mirror of https://github.com/sveltejs/svelte
perf: don't use tracing overeager during dev (#17183)
* perf: don't use tracing overeager during dev #17176 is a case where many sources are created and then written to (due to Svelte 4 prop mechanics), and our tracing kicked in eagerly. That combined with the excessive depth of the related stack traces slowed things down tremendously. The fix is simple: Don't record stack traces until we've seen this source get updated for a couple of times. Additionally we now delete the `updates` map after a flush. Previously it was just an ever-growing stack trace map. * fix * fixpull/16743/merge
parent
3b4b0adcd5
commit
ebb97a618c
@ -0,0 +1,5 @@
|
|||||||
|
---
|
||||||
|
'svelte': patch
|
||||||
|
---
|
||||||
|
|
||||||
|
perf: don't use tracing overeager during dev
|
||||||
Loading…
Reference in new issue