wrapper-2.0 crashed with SIGSEGV in g_list_foreach()

[Guybrush88]

I got this crash twice in a row just after having installed recent updates, I simply received the notifications about the crash

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: libxfce4panel-2.0-4 4.13.4-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Sep 25 12:55:16 2019
ExecutablePath: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
InstallationDate: Installed on 2019-08-30 (25 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcCmdline: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libwhiskermenu.so 1 12582919 whiskermenu Menu\ Whisker Mostra\ un\ menu\ per\ accedere\ facilmente\ le\ applicazioni\ installate
SegvAnalysis:
 Segfault happened at: 0x7f20d86d9be0 <g_list_foreach+16>: mov 0x8(%rdi),%rbx
 PC (0x7f20d86d9be0) ok
 source "0x8(%rdi)" (0x00000025) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-panel
StacktraceTop:
 g_list_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_list_free_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgarcon-1.so.0
 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_value_unset () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: wrapper-2.0 crashed with SIGSEGV in g_list_foreach()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
mtime.conffile..etc.apport.crashdb.conf: 2019-09-22T14:19:18.194237
separator:

[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 #1821686, 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.