Process gets killed after a while when parsing a large xcactivitylog about xclogparser HOT 3 CLOSED

Hi, yes JSONEncoder has memory issues with large documents. I added a flag to truncate Notes (and Warnings and Errors) from the final JSON #151
We also have the --omit_notes flag that you can pass to completely skip notes.

from xclogparser.

I have found the exact line causing the problem – line 192 in HtmlReporter.writeTargetFiles. Encoding the flattened target into a JSON representation seems to eat through my machines RAM. RAM usage rises steadily until the process is eventually killed by the system.

from xclogparser.

I've found the culprit. One of the targets contained around 40000 notes. Seems like JSONEncoder just can't handle such a big amount of data at one time.

I filtered out substeps with 10000 notes or more and XCLogParser was able to create the HTML report. Yay!

Do we even need the notes when dumping into an HTML file? Maybe we could just get rid of them altogether. Or introduce some kind of culling/filtering logic. As of right now, it seems projects with very verbose build phases are incompatible with XCLogParser.

from xclogparser.