midori is very CPU intensive (GTK2)
Bug #1103102 reported by
claive alvin polo acedilla
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Midori Web Browser |
Incomplete
|
Undecided
|
Unassigned |
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
summary: |
- midori0.4.7 is very CPU intensive + midori is very CPU intensive GTK2 |
summary: |
- midori is very CPU intensive GTK2 + midori is very CPU intensive (GTK2) |
To post a comment you must log in.
about:version
Version numbers in brackets show the version used at runtime.
Command line /usr/pbi/ midori- i386/bin/ midori midori_ f50937ae940c0c9 8ca301d941ea51d 8e__0) 18.0.1025. 133 Safari/534.26 Midori/0.4 H264 [x] Ogg Theora [x] WebM [x] (null)
Midori 0.4.7 (de.twotoasts.
GTK+ 2.24.6 (2.24.6) Glib 2.28.8 (2.28.8)
WebKitGTK+ 1.4.3 (1.4.3) libsoup 2.34.3
cairo 1.10.2 (1.10.2)
gcr libunique 1.1.6
granite X11;
libnotify FreeBSD
single instance i386
Platform Mozilla/5.0 (X11; FreeBSD) AppleWebKit/534.26 (KHTML, like Gecko) Chrome/
Identification X11;
Video Formats i386
Netscape Plugins:
npwrapper. libflashplayer. so Shockwave Flash .invalid about:geolocati on about:paths
about:widgets about:private error:nodocs http://