vlc crashed with SIGSEGV in QtSharedPointer::ExternalRefCountData::getAndRef()

[Xavier]

I did nothing diferent as usual ...

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: vlc-bin 3.0.1-3build1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Apr 15 22:37:52 2018
ExecutablePath: /usr/bin/vlc
InstallationDate: Installed on 2012-11-20 (1972 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcCmdline: /usr/bin/vlc --started-from-file /media/username/TOSHIBA\ EXT/lion/Lion.2016.HDRip.XviD.AC3-EVO.avi
SegvAnalysis:
 Segfault happened at: 0x7ff5661dc698 <_ZN15QtSharedPointer20ExternalRefCountData9getAndRefEPK7QObject+8>: mov 0x68(%rbp),%rbx
 PC (0x7ff5661dc698) ok
 source "0x68(%rbp)" (0x0000006b) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
 QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QWindowPrivate::connectToScreen(QScreen*) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 QWindowPrivate::setTopLevelScreen(QScreen*, bool) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
 () at /usr/lib/x86_64-linux-gnu/vlc/plugins/gui/libqt_plugin.so
 () at /usr/lib/x86_64-linux-gnu/vlc/plugins/gui/libqt_plugin.so
Title: vlc crashed with SIGSEGV in QtSharedPointer::ExternalRefCountData::getAndRef()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd 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 #1758152, 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.