ares-inspect makes emulator app UI unresponsive (flicker → black screen) even on minimal generated app

[gondesim]

Summary

I am starting webOS TV development and I am seeing what looks like an emulator/inspect tooling issue.

My app runs normally in emulator until I attach inspector with ares-inspect.
After inspector is attached, UI interaction degrades quickly:

1. input starts lagging / not reflected in UI
2. screen flickers
3. app becomes fully unresponsive, often black screen

I reproduced the same behavior with a minimal app generated via ares-generate and a single HTML button.

This does not reproduce the same way in Simulator, where the app remains usable even with inspector open.

Environment

• OS: Windows 11
• webOS Studio VS Code extension: webossdk.webosstudio v2.1.2
• webOS CLI (ares-*): 3.2.3
• Node.js: v20.18.0
• Emulator: webOS TV Emulator v6.0.0
• Simulator: webOS_TV_24_Simulator
• Oracle VM VirtualBox: v6.1.50 r161033 (Qt5.6.2)

Minimal Repro Project

Attached:
catvusa-inspect-smoke.zip

(Contains generated basic app with small index.html update: one clickable button logging to console.)

Reproduction Steps

1. Package minimal app:

ares-package -o inspect-smoke inspect-smoke

2. Install:

ares-install --device emulator com.catvusa.inspectsmoke_0.0.1_all.ipk

3. Launch:

ares-launch --device emulator com.catvusa.inspectsmoke

4. Confirm app works (click button a few times).

5. Attach inspector:

ares-inspect --device emulator --app com.catvusa.inspectsmoke

6. Continue interacting with app (mouse/remote clicks).

Expected Behavior

App UI should remain responsive while inspector is attached.
Button actions should continue to work and UI should remain visible.

Actual Behavior

After inspector attachment:

• UI stops responding correctly
• flickering begins
• black screen / total unresponsiveness occurs after a few interactions

Sometimes console clicks are still briefly visible before full failure.

Frequency

• Reproduces consistently (or near-consistently) on emulator with inspector attached.
• Reproduced on both real app and minimal generated app.

Additional Notes

• Because issue reproduces in a minimal generated app, this appears not app-specific.
• Behavior strongly points to emulator + inspector interaction issue rather than application logic.