Daniel Peñalba

Yes. Using a memory profiler should be easy to identify who is retaining the reference.

@ArchLeaders any updates on this?

@grokys we don't need this PR anymore. But probably you still want to merge it since this API helps anyone trying to use both flat/hierarchical rows in the future. What...

Note that under windows, the resize is normal: 

@grokys do you think [this PR ](https://github.com/AvaloniaUI/Avalonia/pull/11509) resoves this issue?

Yepp. We should try to update to the latest version of the grammar from VSCode repository to see if this fixes the issue.

Yeah, you're right. We're using the same version [as VSCode](https://github.com/microsoft/vscode/tree/main/extensions/yaml/syntaxes) (the latest). So I guess then the problem might be in the parsing engine. To fix it, we'll need to...

We can replace our shipped grammar with the new one.

Guys, you should try [v1.0.61](https://www.nuget.org/packages/TextMateSharp/1.0.61). It ships #70, so TextMateSharp now supports WASM and includes native libs for each dotnet (6.0, 7.0, 8.0).

I bumped the new onigwrap version in a new [TextMateSharp v1.0.61](https://www.nuget.org/packages/TextMateSharp/1.0.62). Thanks guys.