[Kget] Memory leaks?

[Lukas Appelhans]

> ################
> ==9590== 15,418 (140 direct, 15,278 indirect) bytes in 7 blocks are
> definitely lost in loss record 126 of 187
> ==9590==    at 0x40277EE: operator new(unsigned) (in /usr/lib/valgrind/x86-
> linux/vgpreload_memcheck.so)
> ==9590==    by 0x7DC15D2:
> TransferKioFactory::createTransferHandler(Transfer*, Scheduler*)
> (transferKioFactory.cpp:50)
> ==9590==    by 0x46C79F8: Transfer::handler() (transfer.cpp:165)
> ==9590==    by 0x46C7A56: Transfer::setTransferChange(int, bool)
> (transfer.cpp:284)
> ==9590==    by 0x7DC0176: TransferKio::start() (transferKio.cpp:38)
> ==9590==    by 0x46C43A6: Scheduler::updateQueue(JobQueue*)
> (scheduler.cpp:199)
> ==9590==    by 0x46D3F1A:
> TransferGroupScheduler::jobQueueAddedJobEvent(JobQueue*, Job*)
> (transfergroupscheduler.cpp:39)
> ==9590==    by 0x46B94E1: JobQueue::append(Job*) (jobqueue.cpp:94)
> ==9590==    by 0x46CCFEF: TransferGroup::append(Transfer*)
> (transfergroup.cpp:98)
> ==9590==    by 0x46C5ABC: TransferTreeModel::addTransfer(Transfer*,
> TransferGroup*) (transfertreemodel.cpp:64)
> ==9590==    by 0x46C0FF2: KGet::createTransfer(KUrl const&, KUrl const&,
> QString const&, bool, QDomElement const*) (kget.cpp:714)
> ==9590==    by 0x46C1599: KGet::addTransfer(QDomElement const&, QString
> const&) (kget.cpp:227)
>
> I did not look into this one but I guess that the problem is similiar to
> the one above.

This one shouldn't happen somehow, don't know...

TransferHandler gets deleted in ~Transfer...

Lukas