1663670 - [traceback] error gzip in read

Status: RESOLVED FIXED

(Socorro :: Processor, defect, P2)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

Sentry report: https://sentry.prod.mozaws.net/operations/socorro-new-prod/issues/9538497/

error: Error -3 while decompressing data: invalid code lengths set
  File "socorro/processor/processor_pipeline.py", line 275, in process_crash
    rule.act(raw_crash, raw_dumps, processed_crash, processor_meta_data)
  File "socorro/processor/rules/base.py", line 65, in act
    self.action(raw_crash, raw_dumps, processed_crash, processor_meta_data)
  File "socorro/processor/rules/mozilla.py", line 363, in action
    memory_report = self._extract_memory_info(
  File "socorro/processor/rules/mozilla.py", line 340, in _extract_memory_info
    memory_info_as_string = fd.read()
  File "gzip.py", line 292, in read
    return self._buffer.read(size)
  File "gzip.py", line 487, in read
    uncompress = self._decompressor.decompress(buf, size)

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

There are two of these at the moment. Seems like the best way to alleviate this is to handle the error and treat it as invalid data. We have the crash report this happened on, so it should be easy to reproduce. Tossing it in the queue to do soon.

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

Attachment: pr 5568: bug 1663670: handle zlib errors when decompressing memory report

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

willkg merged PR #5568: "bug 1663670: handle zlib errors when decompressing memory report" in 1a00827.

Comment 4

[Will Kahn-Greene [:willkg] ET needinfo? me]

I pushed the latest changes to prod in bug #1664250. Marking as FIXED.