cpu & memory usage

[GoogleCodeExporter]

gphotoframe ver. 1.1 Beta 2
Ubuntu 10.10
using only Shotwell plugin with 7,000 photos
...
Memory usage(MiB): 23...46...24...64...24...28...24...46...24...46...65

CPU usage is fine for the most part, occasional spike then goes back to 0.

Now the problem. Opening a picture with EOG, gphotoframe cpu usage goes up to 
between 98 to 100% and stays there forever.  Only solution is to close the 
program and run again.  It happens every time.

Would be nice if it would use double-click to open a picture and of course 
multiple gphotoframes to decorate the desktop without the high cpu & memory 
usage.

Original issue reported on code.google.com by cmp...@gmail.com on 8 Oct 2010 at 4:01

[GoogleCodeExporter]

> Memory usage(MiB): 23...46...24...64...24...28...24...46...24...46...65

What command did you use to get this infomation?

> Now the problem. Opening a picture with EOG, gphotoframe cpu usage goes up to 
> between 98 to 100% and stays there forever.  
> Only solution is to close the program and run again.  It happens every time.

I can not reproduce the problem on my Debian squeeze box.
If you use any hardware acceleration, try to turn it off or
uninstall python-clutter-gtk.

Original comment by yendo0206 on 8 Oct 2010 at 4:25

[GoogleCodeExporter]

I used System Monitor to observe the gphotoframe process.

According to my Synaptic Package Manager, python-clutter-gtk is not installed.
I changed my Visual Effects to None in the Appearance Preferences. I exited my 
Cairo Dock. I don't know how to turn off hardware acceleration.  I opened a 
picture again from gphotoframe and same thing happens with cpu usage, 98-100% 
constant.

Maybe something's just messed up with my Ubuntu.  I'll try this again next week 
when I have a fresh install of Maverick final version.

I'm using XDeskPhoto in Windows 7. It's an abandoned program. With 6 picture 
frames displayed on my desktop, it uses only 388KB memory, 0% cpu usage and 
only one instance of this program shows up in Task Manager. Link to this 
program: http://download.cnet.com/XDeskPhoto/3000-12511_4-10525643.html

Original comment by cmp...@gmail.com on 8 Oct 2010 at 6:24

[GoogleCodeExporter]

Thanks for your reporting.

>>>> Memory usage(MiB): 23...46...24...64...24...28...24...46...24...46...65
>>
>>What command did you use to get this infomation?
>
> I used System Monitor to observe the gphotoframe process.

gphotoframe uses Python and PyGtk which use large memory.
On my Debian Squeeze Desktop, gphotoframe use from 25 to 40 Mib memory.
Your case is usual. 

> I opened a picture again from gphotoframe and same thing happens with cpu 
usage, 98-100% constant.
> Maybe something's just messed up with my Ubuntu.  I'll try this again next 
week when I have a fresh install of Maverick final version.

I have no idea at present.  I wait your report. 

Original comment by yendo0206 on 10 Oct 2010 at 11:41

[GoogleCodeExporter]

I just did a fresh install of Ubuntu Maverick final.

I ran gphotoframe 1.1-b3 and only enable Shotwell plugin with over 6,000 photos.

%cpu usage: 0...10...0...8...0...6...0...18...0...8...0...

As soon as I open a picture, gphotoframe %cpu becomes 98-100% constant.
Closing the picture has no effect.  It stays like that unless I exit 
gphotoframe and run it again.

Original comment by cmp...@gmail.com on 10 Oct 2010 at 7:04

[GoogleCodeExporter]

I confirmed this problem on a VMware Ubuntu 10.10 virtual machine.
It seems to me that this is not a bug of gphotoframe.

  Bug #595845 in cairo (Ubuntu): “libcairo2 1.9.10 makes Ubuntu 10.10 slow"
  https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/595845

Original comment by yendo0206 on 11 Oct 2010 at 3:47

[GoogleCodeExporter]

#4658 (twisted.internet.gtk2reactor conflicts with subprocess.Popen) – Twisted
http://twistedmatrix.com/trac/ticket/4658

Original comment by yendo0206 on 14 Oct 2010 at 12:15

[GoogleCodeExporter]

Original comment by yendo0206 on 14 Oct 2010 at 12:29

• Changed state: Started

[GoogleCodeExporter]

Fixed in revision 683026694f (1.1 beta 4).
gphotoframe uses glib2reactor instead of gtk2reactor on Ubuntu 10.10.

Original comment by yendo0206 on 14 Oct 2010 at 8:07

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by yendo0206 on 14 Oct 2010 at 9:16

[GoogleCodeExporter]

Bug 640738 – glib/gtk + twisted main loop is eating up all CPU when a 
subprocess terminates
https://bugzilla.gnome.org/show_bug.cgi?id=640738

Original comment by yendo0206 on 28 Jan 2011 at 6:42