Lukas Stracke

@thchia you beat me to the answer 😅 I discussed this with team members and we came to the conclusion that the intention behind the `timeoutWarningLimit` is indeed to subtract...

Hi @henry-alakazhang thanks for writing in! The reason why we need this timeout (`finalTimeout`) is because our `BrowserTracing` integration starts `IdleTransaction`s on navigations and pageloads that finish themselvse (as opposed...

>I'm curious though if there's a reason the `finalTimeout` continues to run even when the `IdleTransaction` is done. Before v7 there was still a max duration but it didn't seem...

Hey @xr0master thanks for writing in! Unfortunately this is going to be quite hard to figure out without a reproducible example. Any chance you could provide one? Another question: >...

@xr0master thanks for the repro and for all the details! Debugging such leaks is very hard but we'll try to get to the bottom of this. One question though: Did...

Hey thanks a lot for everyone's input so far! Based on your replies, I think we can narrow things down a little bit and we'll try to get this prioritized...

Take what I write here with a grain of salt but to me it kinda makes sense that the incorrect order causes issues. The `requestHandler` creates a new async context/execution...

@sarunast did you check the order of our handlers as described in [this comment](https://github.com/getsentry/sentry-javascript/issues/10790#issuecomment-2014325828) above?

> As you said it's next.js so we don't configure it for express Apologies, I completely missed this in your first comment. Unfortunately, I think we're talking about multiple different...

Hi @jxdp thanks for writing in! Adding some kind of batch-processing to the SDK would require a lot of core functionality changes which I don't think we're going to add...