EffectivelyEfficient

**Use cases** - If people want performance they are likely to want to switch to Transaction Isolation Levels - READ COMMITTED. Sometimes this needs to be done at the connection...

Here is a minimal repro project that illustrates the problem. https://github.com/EffectivelyEfficient/BugBlazorNavigationExceptionFromFinalizer On my machine it reproduces the problem reliably and within a few seconds.

Also note this is for a non-streaming scenario. This means there is no `@attribute [StreamRendering]` on Index.razor. Putting `@attribute [StreamRendering]` on Index.razor stops the error, but it also prevents navigationManager.NavigateTo()...

I got the following message from v1.6.8, but not from v1.6.7. This is using esm and the npm package mysql2, ```typescript const [tableNames] = await mysqlPool().query(· ^··· SyntaxError: Unexpected token...