CPU consumption is too high

Bug #481002 reported by V Sauta
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bochs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: bochs

After I load bochs and start simulation, it is very high CPU usage by Xorg. I am using bochs-x. And even after simulation is stopped, but graphical window is still opened, situation doesn't change: Xorg continues to consume CPU. But when I kill bochs-bin CPU usage returns to its normal behavior.

bochs version: 2.4.1-1ubuntu1
boch-x version: 2.4.1-1ubuntu1
xorg version: 1:7.4+3ubuntu7

ProblemType: Bug
Architecture: amd64
CheckboxSubmission: 08a4b168952f3739e796d2983a33e776
CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
Date: Thu Nov 12 00:52:43 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: bochs 2.4.1-1ubuntu1
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: bochs
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:1625): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1734): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1767): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (rhythmbox:1902): Rhythmbox-WARNING **: Client failure: Не удалось соединиться с демоном
 (evince:2497): Gtk-WARNING **: Unable to retrieve the file info for `file:///tmp/file7ZUUfE.pdf': Произошла ошибка при получении сведений о файле «/tmp/file7ZUUfE.pdf»: No such file or directory

Revision history for this message
V Sauta (tsukushima) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bochs (Ubuntu):
status: New → Confirmed
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.