brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset()

[Barbara Harris-Pruitt]

Ubuntu Mate Beta-1

I expected the Brisk menu to open.
The Brisk menu crashed when I clicked on the icon to open it.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mate-applet-brisk-menu 0.5.0-6ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Mar 18 19:35:43 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
InstallationDate: Installed on 2018-03-18 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1)
ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f8d135abe8e <g_slice_free_chain_with_offset+190>: mov (%r14,%rax,1),%rbp
 PC (0x7f8d135abe8e) ok
 source "(%r14,%rax,1)" (0x3fd333333333333b) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: brisk-menu
StacktraceTop:
 g_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724262, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.