Skip to content

qt-core, webview: Keep the trace's file name in the QtProfiler viewer - #1

Merged
benchoq merged 1 commit into
benchoq:ben_1103_qtprofiler_integrationfrom
Maddimax:ben_1103_qtprofiler_integration
Nov 4, 2026
Merged

benchoq merged 1 commit into
benchoq:ben_1103_qtprofiler_integrationfrom
Maddimax:ben_1103_qtprofiler_integration

Conversation

@Maddimax

@Maddimax Maddimax commented Nov 4, 2026

Copy link
Copy Markdown

The viewer picks its parser by file name: a name ending in .qtd is read as XML, anything else as the compressed .qzt format. The webview wrote every trace to /traces/trace.qtd, so a .qzt trace was parsed as XML and failed with "Encountered incorrectly encoded content".

Write the trace under its real file name instead.

Assisted-by: Claude Code
Change-Id: I68fac9804b3c3f91aafb383efe2c266cf8d3a662

Description

Related issue

Type of change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Breaking change (fix or feature that would change existing behavior)
  • Documentation update
  • Other (please describe)

Checklist

  • I have read the contribution guidelines.
  • My changes follow the code style of this project (npm run ci-lint:all passes).
  • I have tested my changes locally. ([ ] Windows, [ ] Linux, [] MacOS)
  • I have updated the documentation where necessary.

The viewer picks its parser by file name: a name ending in .qtd is read
as XML, anything else as the compressed .qzt format. The webview wrote
every trace to /traces/trace.qtd, so a .qzt trace was parsed as XML and
failed with "Encountered incorrectly encoded content".

Write the trace under its real file name instead.

Assisted-by: Claude Code
Change-Id: I68fac9804b3c3f91aafb383efe2c266cf8d3a662
@benchoq
benchoq merged commit 09bb78a into benchoq:ben_1103_qtprofiler_integration Nov 4, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants