Champion Level 3As a workaround, avoid inspecting the table variable using Alt+W or the Watch/Evaluate window during debugging. Instead, log specific values (e.g., Log.Message(t('col', 0))) or copy small subsets of the data into simple variables or arrays for inspection, since normal execution and TestExecute runs are not impacted.
From what’s been shared, this looks less like a data or scripting issue and more like a debugger-related problem on Windows 11. The crash only occurs when evaluating a populated table variable during a paused debug session, while the same code runs fine outside debug and on Windows 10. That strongly points to how TestComplete’s debugger is trying to evaluate or serialize the table object rather than how the data is being created or stored.
To help others reproduce and narrow this down, it would be useful to isolate the exact trigger by simplifying the scenario step by step: try a table with just one column and one row, then gradually increase columns and rows to see when it starts failing; check whether accessing a single cell versus evaluating the whole table makes a difference; and confirm whether the crash only happens when using Alt+W versus hovering or logging values. This should help determine whether the issue is tied to table size, structure, or the debugger’s evaluation behavior.
Hassan_Ballan
Let's go to the results.
Regarding log.Message, I had already tried using it, but I can only get a value without a breakpoint in debug mode. If there's a breakpoint, it doesn't even return the value of the table field and freezes/closes TestComplete.
I hadn't thought of leaving only one column, but I did it now leaving only one column of the table and the same problem occurs when accessing via Alt+W. Even with a breakpoint, without using Alt+W to inspect, the same problem occurs; TestComplete freezes/closes.
