[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] Does anybody know the state of Akregator maintenance?
From:       Martin Steigerwald <Martin () lichtvoll ! de>
Date:       2010-06-15 7:47:04
Message-ID: 201006150947.14399.Martin () lichtvoll ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hello Frank!

Thanks for your answer.

Am Donnerstag 10 Juni 2010 schrieb Frank Osterfeld:
> On Jun 7, 2010, at 10:29 AM, Martin Steigerwald wrote:
> > Hello!
> > 
> > Does anybody know the maintenance state of Akregator? Are any
> > aKregator haxx0rz still with KDE development?
> 
> I am the maintainer, but I am lacking both time and motivation to work
> on it. And nobody else appeared so far to take over.

Ok. That explains it then.

> > I am asking cause
> > 
> > Bug 116482 -  metakit: akregator crashes at startup
> > https://bugs.kde.org/show_bug.cgi?id=116482
> > 
> > collects duplicates like dust without anyone apparently working on
> > it.
> > 
> > Actually I cannot reproduce it at all since ages, Akregator just
> > works for me, but AFAIR there have been several mk4-Files posted
> > that should trigger the problem.
> 
> The issue is known for a long time, and easy to trigger, by using any
> corrupted mk4 file. The problem is that metakit allocates memory after
> reading the size of some value in the db. If that value is bogus,
> which means it's some random value, and far too high most of the time
> and the process either starts to allocate huge amounts of memory or
> just crashes (if the value is above the OS limit), or both. The only
> real solution I see is to move away from metakit to Akonadi. That was
> started (krss) and is now lingering in the akonadi-ports branch, but
> it needs someone with both time and motivation (see above) to complete
> it.

Would it be possible to fix metakit to check for a bogus value as interim 
solution?

You CC'd to KDE PIM mailing list, a public forum. Thus I guess it is okay 
to copy your answer to the bug report so that people know the current 
state. And possibly another developer stumbling upon it may decide to step 
in. Please veto if not. I will wait a bit for other answers that might 
change the situation again.

Is there somebody with time and motivation to work on the Akonadi branch 
of Akkregator / krss?

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

["signature.asc" (application/pgp-signature)]

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]