Editor freezes when trying to open a large report file

[VitorMMOliveira]

Hello,

Lately we are having trouble with build times, and we're trying to use this tool to evaluate what the issue is.
However, our build log file is over 1 GB. We tried to open it with the BuildReportInspector, but it just freezes de editor on each click.

Is there any way we can split the log file or something else along these lines?

[ManasMudaHW]

Hello,
Facing Similar when we have many files in the build, Maybe because all the files fetch asset path and have a redirection for it.
Can u please look into this and fix it in next release.

[todi1856]

As stated in https://github.com/Unity-Technologies/BuildReportInspector/blob/master/README.md, this package is provided as-is and is not longer supported.

[SkowronskiAndrew]

We have also observed internally that the Build Report Inspector is not able to handle large numbers of objects, and the "Source Assets" tab freezes up when attempting to list and summarize too many element.

In those cases looking inside the raw BuildReport file is a way to see the summary information, file list and build steps, which are the main bits of information to see overview of the build. The file by default is saved as Binary but can be converted to Yaml by moving it into the Asset folder, as the Build Report Inspector does. There is also some build summary information in the Editor.log.

For AssetBundles, the UnityDataTools analyze feature works well for large object counts. It uses an SQLite database so millions of objects can be analyzed and queried. That can be useful for navigating the content of what goes into a large build. But it is not aware of build time info.

For player builds it may be necessary to use the BuildReport API to extract and summarize information that is needed from the packedAssets. That can be useful to seeing the total size contributed by certain assets or other information.

Recently the main UI improvements in the build area have been going into Addressables package, that offers a better UI experience when building Asset Bundles.

[SkowronskiAndrew]

#39 should improve this situation because it sets a maximum number of assets and collapses more entries together.
For truly large builds i expect there will still be performance problems until the UI is really overhauled for handling large lists.

[SkowronskiAndrew]

Based on the SourceAsset cleanup I will close this. It should scale to larger projects now.

If there are further performance problems please open new issues, i think further work could be done but at a certain point the build report file is so large that trying to process it inside an Inspector window doesn't really make sense.