Bug 1330560 - Mark as duplicate semantic is often wrong on firefox coredumps
Summary: Mark as duplicate semantic is often wrong on firefox coredumps
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libreport
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-26 13:07 UTC by Christian Stadelmann
Modified: 2017-08-08 14:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 14:21:34 UTC
Type: Bug


Attachments (Terms of Use)

Description Christian Stadelmann 2016-04-26 13:07:43 UTC
Description of problem:
When reporting firefox crashes, libreport tends to mark unrelated bugs as duplicates of bug #1308650. This is clear since the original bug is fixed but libreport keeps marking other crashes as duplicates of this one.

Version-Release number of selected component (if applicable):
firefox-45.0.2-4.fc24.x86_64
abrt-2.8.0-5.fc24.x86_64
libreport-2.7.0-1.fc24.x86_64

How reproducible:
often (~80% of all firefox crashes)

Steps to Reproduce:
1. report any firefox crash

Actual results:
crash is marked as duplicate of bug #1308650

Expected results:
Not all crashes in firefox are duplicates of bug #1308650, so they should not be marked as duplicate.

Additional info:
Firefox recently started using abrt/libreport, previously had its own bug reporting assistant. This was disabled on fedora. This might be the reason this bug didn't occur earlier.

When reporting bugs in firefox, analyze_CCpp very often has to reduce the backtrace depth due to its enormous size. From event_log:

Backtrace is too big (419879 bytes), reducing depth to 512
Backtrace is too big (423975 bytes), reducing depth to 256
Backtrace is too big (423975 bytes), reducing depth to 128
Backtrace is too big (449925 bytes), reducing depth to 64

A possible fix might be for abrt to handle big backtraces more elegantly, not by reducing them to just ~10 stackframes.

Comment 1 Fedora End Of Life 2017-07-25 20:37:09 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-08-08 14:21:34 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.