Comment 7 for bug 1103102

Hi. Sorry for the late reply.
Yes it is still reproducible.
Below is the about: version result

about:version

Version numbers in brackets show the version used at runtime.

Command line /usr/pbi/midori-i386/bin/midori
Midori midori-0.4.9 ((null))
GTK+ 2.24.17 (2.24.17) Glib 2.34.3 (2.34.3)
WebKitGTK+ 1.8.3 (1.8.3) libSoup 2.40.3
cairo 1.10.2 (1.10.2) libnotify 0.7.3
single instance libunique 1.1.6
Platform X11; FreeBSD i386
Identification Mozilla/5.0 (X11; FreeBSD) AppleWebKit/535.22 (KHTML,
like Gecko) Chrome/18.0.1025.133 Safari/535.22 Midori/"0"."4"
Video Formats H264 [x]   Ogg Theora [x]   WebM [x]

Netscape Plugins:

about:widgets  about:private  about:nodocs  http://.invalid
about:geolocation  about:paths

On 4/25/13, Daniel Fore <email address hidden> wrote:
> OP can you still reproduce this issue with the latest Midori and Webkit?
> If so, can you paste the contents of your current about:version?
>
> ** Changed in: midori
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1103102
>
> Title:
> midori is very CPU intensive (GTK2)
>
> Status in Midori: Webkit Web browser:
> Incomplete
>
> Bug description:
> Steps:
> 1. Open a terminal and run top command
> 2. Open midori beside the terminal
> 3. Open any website in midori
> 4. See the WCPU usage of midori in top
>
> Observed behavior:
> midori eats very high levels of WCPU usage.
> If you open many websites, midori slows down and drag the desktop.
>
> I'm using PC-BSD 9.1 i386 DVD LXDE Virtualbox
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/midori/+bug/1103102/+subscriptions
>