JonasToth added a comment. In D54943#2295894 <https://reviews.llvm.org/D54943#2295894>, @AlexanderLanin wrote:
> Off-Topic: I was just attempting to apply this to my codebase at work. > Seems this will be more challenging than anticipated 😉 > My best guess is this is related to D72730 <https://reviews.llvm.org/D72730> > > Applying fixes ... > terminate called after throwing an instance of 'std::bad_alloc' > what(): std::bad_alloc Lets start with this one: What did you exactly do? Is this a run of `run-clang-tidy` for a whole codebase? In the end, it could actually just boil down to "not enough ram", because `clang-apply-replacements` do merge the diagnostics and stuff at some point. Could you please provide more information about your issue here so that it is possible to root out other issues than memory-limitations. Even those should be addressed in some way. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D54943/new/ https://reviews.llvm.org/D54943 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
