100% cpu from oxide-renderer

Bug #1342195 reported by Michael Vogt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
New
Undecided
Unassigned

Bug Description

When I open the browser on image r131 on the default page I see 100% cpu consumed by:
"""
 2817 ? Sl 2:28 | \_ /usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --type=renderer --disable-accelerated-video-decode --enable-overlay-scrollbar --enable-pinch --enable-viewport --enable-viewport-meta --main-frame-resizes-are-orientation-changes --enable-deferred-image-decoding --lang=en-US --form-factor=phone --enable-pinch --enable-threaded-compositing --enable-delegated-renderer --enable-impl-side-painting --channel=2755.2.714364223
"""

even if the page appears to be fully rendered

Revision history for this message
Olivier Tilloy (osomon) wrote :

I cannot reproduce here on a Nexus 7 with image 134 (the oxide-renderer process, when idle, consumes ~ 5% CPU).

On which device are you seeing this? Can you reliably reproduce across reboots?

Revision history for this message
Michael Vogt (mvo) wrote :

This happens on a nexus4. Image is r131 still and it appears it only happens when I kill the browser and start it again (kill via the GUI by long pressing in the apps "recent" section and tapping on the close icon. I.e. not when the browser is run initially. I will update to the latest image too see if that helps.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.