Summary: | Discover crashes at startup with memory corruption ("corrupted size vs. prev_size") | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Patrick Silva <bugseforuns> |
Component: | discover | Assignee: | Aleix Pol <aleixpol> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | ajcm73, aleks.lecha, blackisle, claylson.martins, elrefaei.omar, gabr0, gabrielmasquediez, genesoo77072, hnrbesing, j.l.vanderzwan, jr, kde, khalid.zubair, klaussemmler, kristopher.ives, lusierra77, nate, nimbosa, sevaor, stefanperales, thecyberd3m0n, wdd5988 |
Priority: | VHI | ||
Version: | 5.13.5 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
valgrind log
valgrind log New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Patrick Silva
2018-09-09 03:00:12 UTC
*** Bug 398373 has been marked as a duplicate of this bug. *** *** Bug 398398 has been marked as a duplicate of this bug. *** *** Bug 398461 has been marked as a duplicate of this bug. *** *** Bug 398463 has been marked as a duplicate of this bug. *** *** Bug 398464 has been marked as a duplicate of this bug. *** *** Bug 398488 has been marked as a duplicate of this bug. *** *** Bug 398549 has been marked as a duplicate of this bug. *** This is a memory corruption, most likely a double-free(). A valgrind log would be nice if anyone can reproduce it. Created attachment 114923 [details]
valgrind log
Created attachment 114924 [details]
valgrind log
*** Bug 398562 has been marked as a duplicate of this bug. *** *** Bug 398564 has been marked as a duplicate of this bug. *** Created attachment 114946 [details]
New crash information added by DrKonqi
plasma-discover (5.13.5) using Qt 5.11.1
- What I was doing when the application crashed:
Opening Discover results in a crash, as does attempting to install any packages.
-- Backtrace (Reduced):
#6 0x00007fb43d70b428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7 0x00007fb43d70d02a in __GI_abort () at abort.c:89
[...]
#9 0x00007fb43d7549dc in malloc_printerr (ar_ptr=0x7fb43da9ab20 <main_arena>, ptr=0x32038c0, str=0x7fb43d863c75 "corrupted size vs. prev_size", action=<optimized out>) at malloc.c:5006
#10 malloc_consolidate (av=av@entry=0x7fb43da9ab20 <main_arena>) at malloc.c:4183
#11 0x00007fb43d757cde in _int_malloc (av=av@entry=0x7fb43da9ab20 <main_arena>, bytes=bytes@entry=4096) at malloc.c:3450
Created attachment 114947 [details]
New crash information added by DrKonqi
plasma-discover (5.13.5) using Qt 5.11.1
Opening Discover or attempting to install any packages results in a crash.
-- Backtrace (Reduced):
#6 0x00007faa23972428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7 0x00007faa2397402a in __GI_abort () at abort.c:89
[...]
#9 0x00007faa239c0781 in malloc_printerr (ar_ptr=0x7faa23d01b20 <main_arena>, ptr=0x37a4c60, str=0x7faa23acac75 "corrupted size vs. prev_size", action=<optimized out>) at malloc.c:5006
#10 _int_realloc (av=av@entry=0x7faa23d01b20 <main_arena>, oldp=oldp@entry=0x37a4c10, oldsize=oldsize@entry=80, nb=nb@entry=144) at malloc.c:4298
#11 0x00007faa239c1839 in __GI___libc_realloc (oldmem=0x37a4c20, bytes=128) at malloc.c:3045
*** Bug 398597 has been marked as a duplicate of this bug. *** *** Bug 398602 has been marked as a duplicate of this bug. *** *** Bug 398607 has been marked as a duplicate of this bug. *** Most likely source of something with that trace is an ABI break in KNS. Can you rebuild plasma-discover from source (from the package is fine) and see if it magically fixes itself? Certainly looks that way: Provider::SearchRequest changed Engine has an instance of that as one of it's member vars directly and not as a pointer: Provider::SearchRequest m_currentRequest; Adding an entry to SearchRequest changes sizeof(Engine) everything is off *kaboom* *** Bug 398639 has been marked as a duplicate of this bug. *** ABI break is in Git so it will be in neon dev unstable, but it has not been in a released version of KDE Frameworks. *** Bug 398653 has been marked as a duplicate of this bug. *** Created attachment 114983 [details]
New crash information added by DrKonqi
plasma-discover (5.13.5) using Qt 5.11.1
- What I was doing when the application crashed:
tried to open updates from KDE tray. Always crashes last time
-- Backtrace (Reduced):
#6 0x00007f229cdf6428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7 0x00007f229cdf802a in __GI_abort () at abort.c:89
[...]
#9 0x00007f229ce4137a in malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f229cf51fe8 "double free or corruption (out)", action=3) at malloc.c:5006
#10 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3867
#11 0x00007f229ce4553c in __GI___libc_free (mem=<optimized out>) at malloc.c:2968
crash is already fixed on neon dev unstable. Yep, we reverted the offending commit. We'll come up with another way to do this. *** Bug 398708 has been marked as a duplicate of this bug. *** Nate, May I ask which commit was reverted? I'm sorry if this information is easy to find in Phabricator I am still learning how to navigate it. Commit 2ad3e66d81b63495a59d012f673af7bd854b53d7 was reverted in knewstuff.git repo. See history at https://cgit.kde.org/knewstuff.git/log/ Created attachment 116417 [details]
New crash information added by DrKonqi
plasma-discover (5.13.5) using Qt 5.11.1
- What I was doing when the application crashed:
Opening Discovery app after update
- Unusual behavior I noticed:
crashes everytime after an update
-- Backtrace (Reduced):
#6 0x00007fbf7b3ac428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7 0x00007fbf7b3ae02a in __GI_abort () at abort.c:89
[...]
#9 0x00007fbf7b3f59dc in malloc_printerr (ar_ptr=0x7fbf7b73bb20 <main_arena>, ptr=0x3192a00, str=0x7fbf7b504c75 "corrupted size vs. prev_size", action=<optimized out>) at malloc.c:5006
#10 malloc_consolidate (av=av@entry=0x7fbf7b73bb20 <main_arena>) at malloc.c:4183
#11 0x00007fbf7b3f8cde in _int_malloc (av=av@entry=0x7fbf7b73bb20 <main_arena>, bytes=bytes@entry=4096) at malloc.c:3450
*** Bug 412625 has been marked as a duplicate of this bug. *** |