Closed Bug 634217 Opened 13 years ago Closed 13 years ago

Change the crash signature max size from 255 characters to 244 characters

Categories

(Socorro :: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 587142

People

(Reporter: scoobidiver, Unassigned)

Details

Currently the crash signature max size in Socorro and the summary max size in Bugzilla are 255 characters.
We are unable to write correctly syntaxed summary in Bugzilla for long crash signatures.
In order to be able to write in the summary: crash [@ signature ], the crash signature size must be limited to 244 characters.
I don't see how we can do this without losing useful information. I think we really ought to get a larger field to use in Bugzilla. :-/
> I don't see how we can do this without losing useful information.
The useful information is in the stack trace.
Without doing that, we see in Socorro crash signatures with no associated bug even if there is one.
For instance:
nsTArray<mozilla::DOMSVGPathSegList::ItemProxy, nsTArrayDefaultAllocator>::Clear() | nsTArray<mozilla::widget::WindowHook::CallbackData, nsTArrayDefaultAllocator>::~nsTArray<mozilla::widget::WindowHook::CallbackData, nsTArrayDefaultAllocator>() | gfxDW...
I'd rather not truncate the Socorro information, that seems short sighted.

Would changing the bugzilla associator script solve the problem?
> Would changing the bugzilla associator script solve the problem?
I don't think so. Indeed, if I have:
* bug X: crash [ @A ]
* 2 crash signatures: Aa, Ab
These 2 crash signatures will be associated to bug X even if they musn't.
If A has 244 characters, there won't be a problem.

If it is easier to extend the Bugzilla summary size to 266 characters, I take.
There are several bugs open already on facets of the signature-length problem, like bug 567012, bug 502820, and bug 587142 (of which this is a direct dupe).
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.