| Summary: | plasma-discover 5.12.5 crashes when opening the flatpak metadatas of one of my games. | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | guillaume+bugs.kde |
| Component: | discover | Assignee: | Aleix Pol <aleixpol> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | guillaume+bugs.kde |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.12.5 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Flatpak files that trigger a crash | ||
|
Description
guillaume+bugs.kde
2018-05-12 20:14:35 UTC
Having a proper backtrace with debug symbols would help and being able to try the flatpak file couldn't hurt. The fact that it's over 9GiB will certainly make it harder to test. Hello, i am sorry for the missing debug symbols, its only installed from archlinux, using repository packages. Unfortunately, i can't send you the .flatpak file for two reasons : 1/ It's size, and the fact that i use internet through 4G connection with monthly quota. Sending you the file would be a nice cut to this quota. 2/ I am currently packaging my linux (proprietary) games, and i can't publish the content ... Best i could do, is providing all the files used to build the package, but for the game itself ... I guess that for 1/, you would expect me to have debug symbols for both plasma-discover and Qt, which would be a huge task for me to do :x Maybe it would be possible to reproduce with a dummy package that would contain random files of big size, that may help... Do you need me to do that ? like a flatpak JSON file that creates multiple GB files from reading /dev/urandom, create the .flatpak file, then trying to open it with discover. That maybe help you to get a repeatable crash. Having a small flatpak file that reproduces the crash would be ideal. Created attachment 112681 [details]
Flatpak files that trigger a crash
Here is what creates a .flatpak file that will make plasma-discover to crash.
What you need to do to build the .flatpak file :
dd if=/dev/urandom bs=1M count=2000 of=file.0
dd if=/dev/urandom bs=1M count=2000 of=file.1
dd if=/dev/urandom bs=1M count=2000 of=file.2
dd if=/dev/urandom bs=1M count=2000 of=file.3
dd if=/dev/urandom bs=1M count=2000 of=file.4
flatpak-builder -v --user --force-clean --arch=i386 --repo=test com.DiscoverCrash.Base DiscoverCrash.json
flatpak build-bundle --arch=i386 test Discover.Crash.flatpak com.DiscoverCrash.Base
Then open Discover.Crash.flatpak with plasma-discover.
There is a thing that seems strange to me : Before crashing, it will allocate a lot of ram (that maybe be the cause of the crash), while we only expect to show the metadata of the package. Is flatpak forcing to map into memory the whole package only to read a small file ? There may have a design problem here
Thanks for the update; changing status. It's a bug in libflatpak, also Gnome Software has the issue. I reported it upstream: https://github.com/flatpak/flatpak/issues/1765 |