Holger Levsen wrote: > I think there is definitly an UI bug in diffoscope here. If/when diffoscope > runs out of memory, it should state that clearly and not throw 42 lines of > traceback at the user.
Good idea. I've added that here: https://salsa.debian.org/reproducible-builds/diffoscope/commit/bb887ddb6e5763b15d4ed9bb448166901dc7253f However: > Note that because of the underlying memory management architecture > (Cās malloc() function), the interpreter may not always be able to > completely recover from this situation; it nevertheless raises an > exception so that a stack traceback can be printed, in case a > run-away program was the cause. > > ā https://docs.python.org/2/library/exceptions.html#exceptions.MemoryError ... so this may not work in all situations. -- o ā¬ ā¬ Chris Lamb o o reproducible-builds.org š ā¬ ā¬ o _______________________________________________ Reproducible-builds mailing list Reproducible-builds@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds