Closed
Bug 557747
Opened 15 years ago
Closed 14 years ago
SkipList of ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ and _NSRaiseError regressed
Categories
(Socorro :: General, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: alqahira, Assigned: lars)
Details
(Keywords: regression)
So, suddenly this week I'm seeing the evil, useless ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ signature again on crash-stats: https://crash-stats.mozilla.com/report/list?version=Camino%3A2.0.2&build_id=&query_search=signature&query_type=exact&query=&date=&range_value=2&range_unit=weeks&process_type=all&plugin_field=&plugin_query_type=&plugin_query=&do_query=&signature=___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___&missing_sig=&page=1
This was set to be discarded/skipped entirely in bug 526046; I'm not sure why it's back :/
Can someone please add this back to the irrelevant frames (and double-check the whole list in bug 526046 comment 9 to make sure they are all still configured properly)? Thanks.
Comment 2•15 years ago
|
||
Lars, can you take a look at this?
Updated•15 years ago
|
Assignee: nobody → lars
Assignee | ||
Comment 3•15 years ago
|
||
"___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___" should be in the irreleventSignatures regular expression in the processor configuration.
Reporter | ||
Comment 4•15 years ago
|
||
https://crash-stats.mozilla.com/query/query?product=ALL&version=ALL%3AALL&platform=mac&range_value=1&range_unit=weeks&date=05%2F05%2F2010+17%3A53%3A56&query_search=signature&query_type=exact&query=___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___&build_id=&process_type=all&do_query=1
shows that there were ~350 crashes in the past week where ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ was the signature, so *something* is broken somewhere along the way :(
All of the ones I looked at should have been given a signature of
"[@ objc_exception_throw | -[NSException raise] | registerNatives ]" (aka the crash from bug 525566).
(I'm not sure if it's related, but I also noticed recently that __ in signature names were ignored in searches (bug 563451); I have no idea if the same/similar code is doing the regexp parsing as is doing the "contains" search.)
Comment 5•15 years ago
|
||
Aravind, can you please change the processor configuation as in comment 3?
Assignee: lars → server-ops
Component: Socorro → Server Operations
Product: Webtools → mozilla.org
QA Contact: socorro → mrz
Target Milestone: 1.7 → ---
Updated•15 years ago
|
Assignee: server-ops → aravind
Comment 6•15 years ago
|
||
We already have this in the list.. Here is the current config value.
irrelevantSignatureRegEx = cm.Option()
irrelevantSignatureRegEx.doc = 'a regular expression matching frame signatures that should be ignored when generating an overall signature'
irrelevantSignatureRegEx.default = '@0x[0-9a-fA-F]{2,}|@0x[1-9a-fA-F]|RaiseException|_CxxThrowException|Abort|___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___|_NSRaiseError|mozilla::ipc::RPCChannel::Call\(IPC::Message\*, IPC::Message\*\)'
Let me know if you need any more information from me.
Updated•15 years ago
|
Assignee: aravind → nobody
Component: Server Operations → Socorro
Product: mozilla.org → Webtools
QA Contact: mrz → socorro
Reporter | ||
Comment 7•14 years ago
|
||
FYI, this is still a problem:
https://crash-stats.mozilla.com/report/list?product=Firefox&platform=mac&query_search=signature&query_type=exact&query=&date=02%2F04%2F2011%2013%3A01%3A08&range_value=1&range_unit=days&hang_type=any&process_type=any&plugin_field=&plugin_query_type=&plugin_query=&do_query=1&admin=1&signature=___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___
http://code.google.com/p/socorro/source/browse/trunk/scripts/config/processorconfig.py.dist#100
irrelevantSignatureRegEx = cm.Option()
irrelevantSignatureRegEx.doc = 'a regular expression matching frame signatures that should be ignored when generating an overall signature'
irrelevantSignatureRegEx.default = '|'.join([
'@0x[0-9a-fA-F]{2,}',
'@0x[1-9a-fA-F]',
'RaiseException',
'_CxxThrowException',
'mozilla::ipc::RPCChannel::Call\(IPC::Message\*, IPC::Message\*\)'
])
That list looks different from the one Aravind quoted in comment 6; at the very least, the ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ and _NSRaiseError entries added in bug 526046 are definitely no longer present in SVN (even though they were in the list Aravind quoted when this bug first appeared).
Reporter | ||
Comment 8•14 years ago
|
||
Here's the corresponding "unskipped _NSRaiseError" reports link:
https://crash-stats.mozilla.com/report/list?product=Firefox&platform=mac&query_search=signature&query_type=exact&query=&date=02%2F04%2F2011%2013%3A01%3A08&range_value=1&range_unit=days&hang_type=any&process_type=any&plugin_field=&plugin_query_type=&plugin_query=&do_query=1&admin=1&signature=_NSRaiseError
Summary: SkipList of ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ regressed → SkipList of ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___ and _NSRaiseError regressed
Comment 9•14 years ago
|
||
In prod:
irrelevantSignatureRegEx.default = '|'.join([
'@0x[0-9a-fA-F]{2,}',
'@0x[1-9a-fA-F]',
'RaiseException',
'_CxxThrowException',
'mozilla::ipc::RPCChannel::Call\(IPC::Message\*, IPC::Message\*\)'
])
Reporter | ||
Comment 10•14 years ago
|
||
Can we get these two frames added back in SVN and then tested and pushed to production at some point, since they're clearly missing now?
Hopefully that will fix it, and if not, at least we'll be no worse off than we were in May of last year/comment 6?
Comment 11•14 years ago
|
||
(In reply to comment #10)
> Can we get these two frames added back in SVN and then tested and pushed to
> production at some point, since they're clearly missing now?
>
> Hopefully that will fix it, and if not, at least we'll be no worse off than we
> were in May of last year/comment 6?
Sorry, my eyes are starting to glaze over from looking at these regexes :)
Can you confirm the two you need are:
___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___
_NSRaiseError
Reporter | ||
Comment 12•14 years ago
|
||
(In reply to comment #11)
> Sorry, my eyes are starting to glaze over from looking at these regexes :)
Mine too ;)
> Can you confirm the two you need are:
>
> ___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___
> _NSRaiseError
Yes, it's those two, added to "irrelevantSignatureRegEx.default"
Thanks again!
Reporter | ||
Comment 13•14 years ago
|
||
Oops, meant to add/reiterate, these two are not as important as bug 631633, so if this bug doesn't make this weekend's push, that's OK (just as long as it makes it at some point) :)
Comment 14•14 years ago
|
||
Reassigning to lars; he's back from vacation and rhelmer is out.
Assignee: nobody → lars
Assignee | ||
Comment 15•14 years ago
|
||
IT request created to carry out this change. Bug 632534
Assignee | ||
Comment 16•14 years ago
|
||
the changes for Comment #12 were completed on Wednesday, Feb 9 at about 8:06am pst.
I think that wraps it up for this bug. If you detect any anomalies, please reopen this bug or file a new one.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 17•14 years ago
|
||
I think this looks good; it appears that those crashes had been appearing fairly regularly at a rate of ~1 every couple of hours, and it doesn't look like there have been any since about 8am PST :-)
I'll keep an eye on it to make sure, but I do think all is finally well here ;) Thanks!
Status: RESOLVED → VERIFIED
Updated•13 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•