Search Issue Tracker

Fixed

Won't Fix in 2022.1.X

Fixed in 2021.3.10f1

Votes

0

Found in

2021.3.0f1

2022.1.1f1

Issue ID

UUM-938

Regression

Yes

[Backport] SyntaxError is thrown when opening buildreport.json

--

-

How to reproduce:
1. Create and build a new Unity project (File > Build Settings... > Build)
2. Open Google Chrome and enter chrome://tracing in the Address Bar
3. Click "Load" and navigate to <Project>/Library/Bee/buildreport.json

Expected result: The buildreport.json file is opened
Actual result: A SyntaxError is thrown

Reproducible with: 2021.2.0b17, 2021.2.16f1, 2022.1.0b13
Not reproducible with: 2021.2.0b16, 2022.2.0a1, 2022.2.0a8
Could not test with: 2019.4.37f1, 2020.3.31f1 (No buildreport.json file is created)

Note: Reproducible with Mono and IL2CPP scripting backend

Error:
SyntaxError: Unexpected token  in JSON at position 3066
at JSON.parse (<anonymous>)
at new TraceEventImporter (chrome://tracing/tracing.js:6283:19)
at Import.createImporter_ (chrome://tracing/tracing.js:2023:8)
at chrome://tracing/tracing.js:2015:167
at Task.run (chrome://tracing/tracing.js:3278:95)
at runAnother (chrome://tracing/tracing.js:3281:371)
at runTask (chrome://tracing/tracing.js:3043:57)
at processIdleWork (chrome://tracing/tracing.js:3048:116)
at window.requestIdleCallback.timeout (chrome://tracing/tracing.js:3041:81)

  1. Resolution Note (2022.1.X):

    Not worth the effort to backport the fixes. The bad characters can be manually removed from the buildreport.json file in the event that someone really wants to view the file. Note that the buildreport.json file is fixed in 2021.3 and 2022.2 onward.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.