Comment 10 for bug 1234542

Well, at least I tried to make soup tracing.

I attach here a *.zip with cmd console & Midori screen shots - made right during some of those hundreds milliseconds when the engines seemed to output in the log most intensively.

I must notice that command line console in "headers" debug mode flows pretty fast when Midori browses through the Web 2.0 - and I see no evident way to process the entire sheet, just because it does not fit into the console window. I can only say that I have not visually noticed any sign of critical malfunction there.
Nevertheless, there are some ЕГГОГs indicated in the very beginning of Midori's start-up process - they are clearly visible on the first shot.