T3 Code v0.0.10 (Windows 10/26100) frequently becomes “Not responding” #980
Description
When running in a longer chain of requests in a thread, the app becomes unresponsive. I am seeing 5 workers running, totaling around 2Gb of memory usage. The unresponsive thread is not the largest, though; it was around 160k. Once the task is complete, the UI recovers. The example thread I have open is ~30k characters total, with one image.
I captured a dump of the main process (T3 Code (Alpha).exe - v 0.0.10) while the UI was frozen.
Main thread (CrBrowserMain) stack excerpt:
v8::ArrayBuffer::Allocator::MaxAllocationSize → cppgc::testing::StandaloneTestingHeap::StandaloneTestingHeap → Cr_z_uncompress → sqlite3_dbdata_init → v8::internal::compiler::... → v8_inspector::V8InspectorClient::consoleAPIMessage → node::FreePlatform
This suggests the UI thread is blocked in V8 / cppgc work (using StandaloneTestingHeap) instead of pumping the Windows message loop, leading to the unresponsive window.
I can provide the full .dmp if helpful. I can also fork and try to diagnose locally if you can't replicate.