Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Sandro Knauß]

Control: usertags -1 fixed-upstream

Hey,

Fix is upstream:

kdepim [Applications/16.08 f68b21d] Akregator keep crashing at exit
akregator [master 36c7fe5] Akregator keep crashing at exit

(upstream had switched repos, so stable and master needs to be applied two 
times)

Regards,

sandro

--
Am Freitag, 2. September 2016, 14:13:31 CEST schrieb Maximiliano Curia:
> Control: tag -1 + pending
> 
> ¡Hola Sandro!
> 
> El 2016-09-02 a las 08:51 +0200, Sandro Knauß escribió:
> > Control: tags -1 +patch
> > 
> > thanks, for the backtrace. This helps to track this down.
> > 
> > I can reproduce this, but currently I can't test the patch for it. But
> > this
> > only happens if akregator is started as single application. My normal way
> > to use akregator is via kontact and this way it does not crash.
> > 
> > I looks that we have to test the partenNode if this is a valid
> > pointer.Akregator::SubscriptionListModel::index
> > 
> > Akregator::SubscriptionListModel::index
> > 
> > add this add line 248:
> >if (!parentNode) {
> >
> >return QModelIndex();
> >
> >}
> 
> Oh, I had came up with the same patch. :)
> I could finally test this, and the patch fixes the segfault. Could you push
> this upstream (for 16.08.1, I guess)?
> 
> Happy hacking



signature.asc
Description: This is a digitally signed message part.

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Maximiliano Curia]

Control: tag -1 + pending

¡Hola Sandro!

El 2016-09-02 a las 08:51 +0200, Sandro Knauß escribió:

Control: tags -1 +patch



thanks, for the backtrace. This helps to track this down.


I can reproduce this, but currently I can't test the patch for it. But this 
only happens if akregator is started as single application. My normal way to 
use akregator is via kontact and this way it does not crash.


I looks that we have to test the partenNode if this is a valid 
pointer.Akregator::SubscriptionListModel::index



Akregator::SubscriptionListModel::index



add this add line 248:
   if (!parentNode) { 
   return QModelIndex(); 
   }


Oh, I had came up with the same patch. :)
I could finally test this, and the patch fixes the segfault. Could you push 
this upstream (for 16.08.1, I guess)?


Happy hacking
--
"There are only two things wrong with C++: The initial concept and the
implementation."
-- Bertrand Meyer
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Processed: Re: Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #836011 [akregator] akregator: Akregator keep crashing at exit, sometimes 
do not save recent feeds
Added tag(s) pending.

-- 
836011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Sandro Knauß]

Control: tags -1 +patch


Hey,

thanks, for the backtrace. This helps to track this down.

I can reproduce this, but currently I can't test the patch for it. But this 
only happens if akregator is started as single application. My normal way to 
use akregator is via kontact and this way it does not crash.

I looks that we have to test the partenNode if this is a valid 
pointer.Akregator::SubscriptionListModel::index

Akregator::SubscriptionListModel::index

add this add line 248:
if (!parentNode) {
return QModelIndex();
}


Regards,

sandro

Am Freitag, 2. September 2016, 00:30:05 CEST schrieb Ismael Bejarano:
> Hola Maximiliano!
> 
> On Thu, Sep 1, 2016 at 6:20 AM, Maximiliano Curia  wrote:
> > ¡Hola Ismael!
> > 
> > El 2016-08-30 a las 01:13 -0300, Ismael escribió:
> >> Package: akregator Version: 4:16.04.3-1 Severity: grave Justification:
> causes non-serious data loss
> 
> >>   * What led up to the situation?
> >> 
> >> Since a recent upgrade (less than a month ago). After reading a feed
> 
> when closing Akregator it will crash without saving feeds state. The next
> time it will load like it didn't fetch any feed.
> 
> >>   * What exactly did you do (or not do) that was effective (or
> 
> ineffective)?
> 
> >> If I remaing in the welcome page I can synchronize without problems, and
> 
> Akregator will close correctly.
> 
> >> But If I read a post from a feed or load the list of post in a folder.
> 
> It will crash when closing Akregator.
> 
> >>   * What was the outcome of this action?
> >> 
> >> Run under gdb generates the following stack trace
> >> 
> >> 
> >> #0  0x7fffd4079f48 in Akregator::SubscriptionListModel::index(int,
> 
> int, QModelIndex const&) const ()   from
> /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so #1
>  0x75dac951 in QTreeView::isRowHidden(int, QModelIndex const&)
> const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
> 
> > Thanks for the report. I can't reproduce the issue here, and sadly the
> 
> gdb output sent doesn't have enough debugging information. Could you please
> install akregator-dbgsym, and qtbase5-dbg and run it under gdb again?
> 
> > The -dbgsym packages are in separated repositories, so you'll probably
> 
> need to add:
> > deb http://debug.mirrors.debian.org/debian-debug unstable-debug main
> > to your sources.list. (For more information [1])
> > 
> > Also, kde applications are heavily threaded so you'll need to ask gdb to
> 
> produce a backtrace for each thread, this can be achieved with:
> > (gdb) thread apply all backtrace
> > (For more information [2])
> > 
> > Happy hacking,
> > [1]: https://wiki.debian.org/AutomaticDebugPackages
> 
> > [2]:
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_usef
> ul_crash_reports
> > --
> > "EIEIO  Go home and have a glass of warm, dairy-fresh milk"
> > -- The GNU C Library Reference Manual, Chapter 2.2, Error Codes
> > Saludos /\/\ /\ >< `/
> 
> Here is a backtrace with requested info in an attachment.
> 
> Like Alexandre said it only happen when you read an article. In my case is
> not 100% but only one or two times it didn't crash.
> 
> Also tried with a fresh account with only planet.debian.org and it still
> crashed in the same place.
> 
> If you need more info just let me know.
> 
> Regards
> 
> Ismael



signature.asc
Description: This is a digitally signed message part.

Processed: Re: Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #836011 [akregator] akregator: Akregator keep crashing at exit, sometimes 
do not save recent feeds
Added tag(s) patch.

-- 
836011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Ismael Bejarano]

Hola Maximiliano!

On Thu, Sep 1, 2016 at 6:20 AM, Maximiliano Curia  wrote:
>
> ¡Hola Ismael!
>
> El 2016-08-30 a las 01:13 -0300, Ismael escribió:
>>
>> Package: akregator Version: 4:16.04.3-1 Severity: grave Justification:
causes non-serious data loss
>
>
>>   * What led up to the situation?
>
>
>> Since a recent upgrade (less than a month ago). After reading a feed
when closing Akregator it will crash without saving feeds state. The next
time it will load like it didn't fetch any feed.
>
>
>>   * What exactly did you do (or not do) that was effective (or
ineffective)?
>
>
>> If I remaing in the welcome page I can synchronize without problems, and
Akregator will close correctly.
>
>
>> But If I read a post from a feed or load the list of post in a folder.
It will crash when closing Akregator.
>
>
>>   * What was the outcome of this action?
>
>
>> Run under gdb generates the following stack trace
>
>
>> #0  0x7fffd4079f48 in Akregator::SubscriptionListModel::index(int,
int, QModelIndex const&) const ()   from
/usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so #1
 0x75dac951 in QTreeView::isRowHidden(int, QModelIndex const&)
const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
>
>
> Thanks for the report. I can't reproduce the issue here, and sadly the
gdb output sent doesn't have enough debugging information. Could you please
install akregator-dbgsym, and qtbase5-dbg and run it under gdb again?
>
> The -dbgsym packages are in separated repositories, so you'll probably
need to add:
> deb http://debug.mirrors.debian.org/debian-debug unstable-debug main
> to your sources.list. (For more information [1])
>
> Also, kde applications are heavily threaded so you'll need to ask gdb to
produce a backtrace for each thread, this can be achieved with:
> (gdb) thread apply all backtrace
> (For more information [2])
>
> Happy hacking,
> [1]: https://wiki.debian.org/AutomaticDebugPackages
> [2]:
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
> --
> "EIEIO  Go home and have a glass of warm, dairy-fresh milk"
> -- The GNU C Library Reference Manual, Chapter 2.2, Error Codes
> Saludos /\/\ /\ >< `/

Here is a backtrace with requested info in an attachment.

Like Alexandre said it only happen when you read an article. In my case is
not 100% but only one or two times it didn't crash.

Also tried with a fresh account with only planet.debian.org and it still
crashed in the same place.

If you need more info just let me know.

Regards

Ismael
Thread 9 (Thread 0x7fff8533f700 (LWP 19274)):
#0  0x7fffeb92b07f in pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7239a933 in JSC::GCThread::gcThreadMain() (this=0xb6a2f0)
at heap/GCThread.cpp:81
#2  0x726c2941 in 
WTF::ThreadSpecific::destroy(void*) (ptr=0x7fffce2a53e0) at 
wtf/ThreadingPthreads.cpp:195
#3  0x7fffeb925444 in start_thread (arg=0x7fff8533f700)
at pthread_create.c:333
#4  0x7449f20d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7fff85b40700 (LWP 19273)):
#0  0x7fffeb92b07f in pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7239a933 in JSC::GCThread::gcThreadMain() (this=0xb3cc50)
at heap/GCThread.cpp:81
#2  0x726c2941 in 
WTF::ThreadSpecific::destroy(void*) (ptr=0x7fffce2a5080) at 
wtf/ThreadingPthreads.cpp:195
#3  0x7fffeb925444 in start_thread (arg=0x7fff85b40700)
at pthread_create.c:333
#4  0x7449f20d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7fff86341700 (LWP 19272)):
#0  0x7fffeb92b07f in pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7239a933 in JSC::GCThread::gcThreadMain() (this=0xb3c750)
at heap/GCThread.cpp:81
#2  0x726c2941 in 
WTF::ThreadSpecific::destroy(void*) (ptr=0x7fffce2a5140) at 
wtf/ThreadingPthreads.cpp:195
#3  0x7fffeb925444 in start_thread (arg=0x7fff86341700)
at pthread_create.c:333
#4  0x7449f20d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7fff86b42700 (LWP 19271)):
#0  0x7fffeb92b07f in pthread_cond_wait@@GLIBC_2.3.2 ()
at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x72399811 in JSC::BlockAllocator::blockFreeingThreadMain() 
(this=0x7fffce303058) at heap/BlockAllocator.cpp:139
#2  0x726c2941 in 
WTF::ThreadSpecific::destroy(void*) (ptr=0x7fffce2a51b0) at 
wtf/ThreadingPthreads.cpp:195
#3  0x7fffeb925444 in start_thread (arg=0x7fff86b42700)
at pthread_create.c:333
#4  0x7449f20d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fffcde79700 (LWP 19270)):
#0  0x7449609d in poll ()
at ../sysdeps/unix/syscall-template.S:84
#1  0x7fffeb1001f6 in 

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Alexandre Detiste]

> Thanks for the report. I can't reproduce the issue here,

Hi,

I'm subscribed to this bug, haven't yet made a trace, but hope this helps:

- when akregator is started, and then closed without opening any news
item, it will close fine, 100% reproducible
- as soon as any news item has been read, it will crash at shutdown,
100% reproducible
so I suspect the problem comes from some khtml/webkit component.

I'll have a look again.

Alexandre

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Maximiliano Curia]

¡Hola Ismael!

El 2016-08-30 a las 01:13 -0300, Ismael escribió:
Package: akregator 
Version: 4:16.04.3-1 
Severity: grave 
Justification: causes non-serious data loss



  * What led up to the situation?


Since a recent upgrade (less than a month ago). After reading a feed when 
closing Akregator it will crash without saving feeds state. The next time it 
will load like it didn't fetch any feed.


  * What exactly did you do (or not do) that was effective (or 
ineffective)?


If I remaing in the welcome page I can synchronize without problems, and 
Akregator will close correctly.


But If I read a post from a feed or load the list of post in a folder. It will 
crash when closing Akregator.



  * What was the outcome of this action?



Run under gdb generates the following stack trace


#0  0x7fffd4079f48 in Akregator::SubscriptionListModel::index(int, int, 
QModelIndex const&) const () 
  from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so 
#1  0x75dac951 in QTreeView::isRowHidden(int, QModelIndex const&) const 
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 


Thanks for the report. I can't reproduce the issue here, and sadly the gdb 
output sent doesn't have enough debugging information. Could you please 
install akregator-dbgsym, and qtbase5-dbg and run it under gdb again?


The -dbgsym packages are in separated repositories, so you'll probably need to 
add:
deb http://debug.mirrors.debian.org/debian-debug unstable-debug main
to your sources.list. (For more information [1])

Also, kde applications are heavily threaded so you'll need to ask gdb to 
produce a backtrace for each thread, this can be achieved with:

(gdb) thread apply all backtrace
(For more information [2])

Happy hacking,
[1]: https://wiki.debian.org/AutomaticDebugPackages
[2]: 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
--
"EIEIO Go home and have a glass of warm, dairy-fresh milk"
-- The GNU C Library Reference Manual, Chapter 2.2, Error Codes
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

[Ismael]

Package: akregator
Version: 4:16.04.3-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,


   * What led up to the situation?

Since a recent upgrade (less than a month ago). After reading a feed when
closing Akregator it will crash without saving feeds state. The next time it
will load like it didn't fetch any feed.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?

If I remaing in the welcome page I can synchronize without problems, and
Akregator will close correctly.

But If I read a post from a feed or load the list of post in a folder. It will
crash when closing Akregator.


   * What was the outcome of this action?

Run under gdb generates the following stack trace


#0  0x7fffd4079f48 in Akregator::SubscriptionListModel::index(int, int,
QModelIndex const&) const ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#1  0x75dac951 in QTreeView::isRowHidden(int, QModelIndex const&) const
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2  0x75dac9d7 in QTreeView::isIndexHidden(QModelIndex const&) const ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3  0x75da831c in QTreeView::visualRegionForSelection(QItemSelection
const&) const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x75d6b168 in QAbstractItemView::selectionChanged(QItemSelection
const&, QItemSelection const&) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x75db78da in QTreeView::selectionChanged(QItemSelection const&,
QItemSelection const&) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x75d70750 in
QAbstractItemView::setSelectionModel(QItemSelectionModel*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x75db5977 in QTreeView::setSelectionModel(QItemSelectionModel*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x75d6af45 in QAbstractItemView::setModel(QAbstractItemModel*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x75db5724 in QTreeView::setModel(QAbstractItemModel*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7fffd407843d in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#11 0x7fffd40918bc in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#12 0x7fffd40bc665 in
Akregator::MainWidget::setFeedList(QSharedPointer const&)
()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#13 0x7fffd40bc7ed in Akregator::MainWidget::slotOnShutdown() ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#14 0x7fffd40b2136 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#15 0x7fffd40b2908 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#16 0x7fffd40b2969 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#17 0x74fa6c7c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x74f7fa13 in QCoreApplication::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00408828 in ?? ()
#20 0x743dc700 in __libc_start_main (main=0x4081b0, argc=1,
argv=0x7fffe478, init=, fini=,
rtld_fini=, stack_end=0x7fffe468)
at ../csu/libc-start.c:291
#21 0x00408ac9 in _start ()


   * What outcome did you expect instead?

I'd expect that it didn't crash when closing.




-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages akregator depends on:
ii  kinit5.23.0-1
ii  kio  5.23.0-1
ii  libc62.23-5
ii  libgcc1  1:6.1.1-11
ii  libkf5codecs55.23.0-1
ii  libkf5completion55.23.0-1
ii  libkf5configcore55.23.0-1
ii  libkf5configgui5 5.23.0-1
ii  libkf5configwidgets5 5.23.0-1
ii  libkf5coreaddons55.23.0-1
ii  libkf5grantleetheme-plugins  16.04.3-1
ii  libkf5grantleetheme5 16.04.3-1
ii  libkf5i18n5  5.23.0-1
ii  libkf5iconthemes55.23.0-1
ii  libkf5jobwidgets55.23.0-1
ii  libkf5kcmutils5  5.23.0-1
ii  libkf5kiocore5   5.23.0-1
ii  libkf5kiogui55.23.0-1
ii  libkf5kiowidgets55.23.0-1
ii  libkf5kontactinterface5  16.04.2-1
ii  libkf5libkdepim-plugins  4:16.04.2-3
ii  libkf5libkdepim5 4:16.04.2-3
ii  libkf5messageviewer5 4:16.04.3-2
ii  libkf5notifications5 5.23.0-1
ii  libkf5notifyconfig5  5.23.0-1
ii  libkf5parts5 5.23.0-1
ii