For example, bug 1757610 has at least 5 duplicates.
Looking at the LeakSanitizer outputs, all the "leak at ..." lines are the same, but in a different order.
Because only the first of these lines is used in bug titles, each bug looks different at first glance.

My guess is that the solution may be to sort "leak at" lines in alphabetical orders -- that's how I could quickly determine that my bugs were duplicate.
Could this be done from LeakSanitizer directly? If not, it should probably be done at least before constructing the bug title.

Full logs distinguish between "direct" and "indirect" leaks.
I think it would be useful to expose that detail in the summary "leak at" lines shown in bug descriptions, and the bug title would probably benefit from being chosen from direct leaks (if present) instead of indirect ones.

One other potential improvement would be to remove the low-level memory operations from the title, e.g.: MakeUnique, maybe_pod_realloc, etc. These details are still available in full logs.

The severity field is not set for this bug.
:andi, could you have a look please?

For more information, please visit auto_nag documentation.

Isn't this related with ASan? Is this the right component?

The severity field is not set for this bug.
:decoder, could you have a look please?

For more information, please visit auto_nag documentation.