crash not linked to bugzilla for signature formatted as [@ xxxx], i.e. without trailing space I came across this example: bug 601261, bp-11189a7e-50c4-45b9-bc4d-a0c382110612 more than half of all crash bugs are formatted as [@ xxxx]. And, many people are conditioned to not have a space before the final bracket ]. see https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=substring&keywords=crash&keywords_type=allwords&list_id=494050&short_desc=[%40&field0-0-0=cf_crash_signature&bug_severity=critical&type0-0-1=substring&field0-0-1=keywords&type1-0-1=allwordssubstr&resolution=---&classification=Client%20Software&classification=Components&query_format=advanced&short_desc_type=allwordssubstr&type0-0-0=regexp&value0-0-0=[a-z%2C%29]\]&field1-0-0=short_desc&field1-0-1=short_desc
It should be noted, there are also bugs reports that lack leading space, as in bug 514921 - [10.6.X] Crash [@objc_msgSend | TFSInfo::~TFSInfo() ] however, the crash sig field and socorro seem to be cooperating for that one.
I've spent some time trying to track this down but haven't gotten anything useful. I don't think it is related to the new cron -- many signatures in our unit tests lack a trailing space and are parsed correctly. It's more likely that this is a problem in the web app related to my path for bug 649545. I will dig further after this weeks freeze.
Assignee: nobody → chris.lonnen
(In reply to comment #2) > It's more > likely that this is a problem in the web app related to my path for bug > 649545. I will dig further after this weeks freeze. But that's not landed on production, right? I would have expected that patch in bug 634276 to be at fault...
perhaps another example ... https://bugzilla.mozilla.org/show_bug.cgi?id=536070 + bp-0cee47d0-c1f0-420c-b5e5-70c8f2110613
one more ... PAudioParent bug 596567 + bp-0b21decd-1def-45b2-8db3-1e0272110614 but doesn't seem to be related to trailing space, because I added a space to the signature and the bug# still doesn't appear for bp-0b21decd-1def-45b2-8db3-1e0272110614
That last example is probably bug 669986. If you come across another example please link it without fixing it. After digging a bit more today I don't see anything in the code to cause this, and I cannot find an example of this happening in the wild.
(In reply to Chris Lonnen :lonnen from comment #6) > That last example is probably bug 669986. yes, I believe that is correct > If you come across another example please link it without fixing it. After > digging a bit more today I don't see anything in the code to cause this, and > I cannot find an example of this happening in the wild. THanks for checking. I think we can call this WFM.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.