Hi kithrup,
Yes, it is expected that Instruments should be able to deal with an arbitrary size of a trace bundle, including very large one.
It make sense that it could be tricky to upload 68Gb of trace. But even without the trace a filed bug with steps to reproduce the issue, expectation and screenshot or video of the issue, could be valuable.
If you are interested in Leaks only you can try different approach as a workaround:
- Enable MallocStackLogging by switching it on in Scheme -> Diagnostics -> Malloc Stack Logging or as with environment variable as described in the instruction (https://developer.apple.com/library/archive/documentation/Performance/Conceptual/ManagingMemory/Articles/MallocDebug.html).
- Use Product->Profile in Xcode to open Instruments targeting your app, choose Blank template and add Leaks instrument only. Instruments will inherit the environment variables from Xcode and thus also run with Malloc Stack Logging.
- Run the target process for 2 hours or more. You can also adjust leaks snapshot interval during recording using Snapshots button at the bottom.
The trace file at the end should be much smaller (assuming Allocations instrument contributed a lot to the trace file) and Instruments should work with them without an issue.
If you are interested in Allocations as well, you could try to enable Malloc Stack Logging, let the target app run for 2 hours without Instruments recording, and at the end capture a memgraph as described in the instruction (https://developer.apple.com/documentation/xcode/gathering-information-about-memory-use) and import the memgraph to Instrument or use it in Xcode Memory Debugger.