brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset()

[Quasi Nymus]

The menu sometimes randomly crashes and has to reload.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: mate-applet-brisk-menu 0.4.5-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Apr 14 22:50:21 2018
ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
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
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f89dc62e9df <g_slice_free_chain_with_offset+191>: mov (%rbx,%rax,1),%r12
 PC (0x7f89dc62e9df) ok
 source "(%rbx,%rax,1)" (0x3fd333333333333b) not located in a known VMA region (needed readable region)!
 destination "%r12" 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: sudo users

[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.