[Bug 1899100] Re: whoopsie assert failure: double free or corruption (fasttop)

[Brian Murray]

Looking at the Error Tracker crash buckets linked to from the bug
description the version of the package from focal-proposed and bionic-
proposed does not appear. Additionally, I was unable to find any similar
looking crashes in the Error Tracker so there are no new "double free"
buckets with the version of the package from -proposed. Subsequently,
I'm setting the tags to verification-done.

** Tags removed: verification-needed verification-needed-bionic verification-needed-focal
** Tags added: verification-done verification-done-bionic verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1899100

Title:
  whoopsie assert failure: double free or corruption (fasttop)

Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Bionic:
  Fix Committed
Status in whoopsie source package in Focal:
  Fix Committed
Status in whoopsie source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  whoopsie is crashing somewhat regularly. There are a couple of crashes in the Error Tracker which look similar:

  https://errors.ubuntu.com/problem/5c1f68854a0f3bd5e263f1cd35e4dd944c9e90bd
  https://errors.ubuntu.com/problem/5d7e641dc46229c08389420fdd74a7473d2dec98

  As of yet (2020-11-22) neither crash is happening with whoopsie
  version 0.2.73.

  [Test Case]
  We don't have a manual test case for this crash report but given the number of crashes in the Error Tracker and the number of users of whoopsie the absence of the same crash occurring with the new version of whoopsie should be enough to consider this verified.

  [Regression Potential]
  Whoopsie will no longer upload crash reports with duplicate keys but this was not something it should have been doing in the first place. That being said we should also test whoopsie with a sample of crashes (apport-test-crashes) and ensure they are received by the staging version of the Ubuntu Error Tracker.

  Original Description
  --------------------
  Apport popped up saying whoopsie had crashed (I assume during a previous crash report upload?)

  ProblemType: CrashDistroRelease: Ubuntu 20.10
  Package: whoopsie 0.2.72
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu49
  Architecture: amd64
  AssertionMessage: double free or corruption (fasttop)
  CasperMD5CheckResult: skip
  CrashCounter: 1
  Date: Fri Oct  9 08:08:56 2020
  ExecutablePath: /usr/bin/whoopsie
  InstallationDate: Installed on 2019-11-18 (325 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/bin/whoopsie -f
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
  RelatedPackageVersions: apport-noui N/ASignal: 6SourcePackage: whoopsie
  StacktraceTop:
   __libc_message (action=action at entry=do_abort, fmt=fmt at entry=0x7f5982159128 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
   malloc_printerr (str=str at entry=0x7f598215b5d8 "double free or corruption (fasttop)") at malloc.c:5389
   _int_free (av=0x7f598218bba0 <main_arena>, p=0x55964a2bf3e0, have_lock=0) at malloc.c:4298
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_remove_all () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: whoopsie assert failure: double free or corruption (fasttop)
  UpgradeStatus: Upgraded to groovy on 2020-10-06 (2 days ago)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1899100/+subscriptions