[WebKit-devel] [Bug 227947] browserbenchmark "peacekeeper" causes crash in the first stage

[Andrea Diamantini]

https://bugs.kde.org/show_bug.cgi?id=227947





--- Comment #10 from Andrea Diamantini <adjam7 gmail com>  2010-04-26 11:14:13 ---
On Monday 26 April 2010 01:56:33 Dawit Alemayehu wrote:
> https://bugs.kde.org/show_bug.cgi?id=227947
> 
>  ...
>
> > rekonq(2259)/kio (Scheduler) KIO::SchedulerPrivate::cancelJob: Doing
> > nothing because I don't know job KIO::TransferJob(0xae80668)
> 
> I get that a lot too with Konqueror + kwebkitpart. It is benign and you can
> ignore it. It seems to be debug statement that comes from a sanity check to
> prevent multiple deletion of an already deleted ioslave...

Ok, thanks for info.

> > So, without having read 1 line of code about yet, situation seems the
> > following:
> > - kio::scheduler doesn't "know" rekonq requests, while "knows"
> > konqueror's ones.
> 
> I am not familiar with the new scheduler code because it has been
> re-written for KDE 4.5 by Andreas, but the above statement does not make
> any sense if you look at the code. You can effectively ignore the
> bogus/unclear debug for the reasons I stated above. Anyhow, it is entirely
> possible the bug stems from this scheduler rewrite. With all the new
> functionality and features added to it, the schduler has become more
> complicated than it was... More complications/features almost always by
> definition entails the introduction of new bugs. I know because I have
> been stuck fixing a lot of bugs in kio_http which was re-written for KDE
> 4.

I'm not familiar with KIO code at all. And I have to say it's really difficult 
to understand and debug.

> Can you try to comment out the deprecated KIO::Scheduler::scheduleJob(...)
> from KIO::AccessManager::createRequest and see if that makes any
> difference in your case ? I doubt it, but never hurts to try...

Sure. Thanks for hints and feedback.
Regards,

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.