🦋 Changeset detected

Latest commit: 5d4e61e

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Playground

pnpm add https://pkg.pr.new/svelte@16531

Won't the issue return when we have multiple apps mounted one inside another?
It doesn't create a permanent leak, so it is ok as is.

I see what you mean, thanks for pointing that out!

We should also probably check what happens (i don't know if it can even happen) when you have multiple even listeners fire

I did this and it is super weird - sometimes one click results in dozens of runs.
Edit: Seems not unmounting the app has badly interfered with the result. Now it's better, but still multiple runs per click.

I'm working on developing a complex application with a UI layer built using Svelte. This application is intended to be packaged and provided as a library for others to use, and it will be repeatedly initialized and destroyed. While checking for memory leaks in my application, I found that last_propagated_event is causing major interference. In the memory snapshots captured by Chrome DevTools, most of the data retained are references from last_propagated_event, which makes it difficult for me to quickly locate the information I need. On the other hand, after users initialize and then destroy the application, memory usage does not drop due to the lingering references from last_propagated_event, it negatively impacts the user experience.

But it isn't a constantly growing leak, right?

I confirm the underlying bug is fixed in Firefox 141.0.3, so I think we can revert this fix in one or two weeks.