Comment 1 for bug 196489

Thank you for your report. However, crash reports can have more information in them which potentially have sensitive information, in particular in the Tracebacks (python) or core dumps (SIGSEGV, etc.). Bug 132800 has been fixed, but (1) bugs were filed privately since long before already, and (2) we cannot filter core dumps like we can filter ProcCmdline, etc.

While I acknowledge that the weirdness you reported exists, we won't file bugs as public by default for above reasons. Developers usually set high-profile crashes like this to public after inspecting that there is no sensitive data (this already happened for bug 196335).

Thanks,

Martin