Closed Bug 615327 Opened 14 years ago Closed 14 years ago

Socorro - unstable processor behavior for unexpected crash type values

Categories

(Socorro :: General, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: lars, Unassigned)

References

Details

The current processor will barf on a crash if the crash type is anything but 'plugin' or empty.  There is a code path where execution can drop through the end of the function 'insertCrashProcess' and not return a proper value.
fixed in r2796 
this will appear in 1.7.6
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Blocks: 578687
Lars: is this a strict dupe of bug 580711?
no this is not a strict duplication of that bug.  This bug was about the backend not choking on a 'jetpack' or 'content' crash.  Bug 580711 is about the semantic handling of one of those crash types.  Bug 580711 may be just a UI bug.
I'd still like this to be deployed earlier than 1.7.6 if possible, so that I can land bug 614610.
Blocks: 614610
This has been pushed up to 1.7.5.3 which is targeted for a production push on Thursday.
This fix is now live in production and verified to be functioning.
Status: RESOLVED → VERIFIED
Component: Socorro → General
Product: Webtools → Socorro
You need to log in before you can comment on or make changes to this bug.