- **labels**: Pixes (pix_ objects) --> Pixes (pix_ objects), pix_image, CPU
- **assigned_to**: IOhannes m zmölnig
- **OS**: --> linux
- **Release**: linux --> 0.92.3
---
** [bugs:#144] pix_image eats a lot of CPU even when idle**
**Status:** closed-fixed
**OS:** linux
**Release:** 0.92.3
**Labels:** Pixes (pix_ objects) pix_image CPU
**Created:** Fri May 27, 2011 07:50 PM UTC by Matteo Sisti Sette
**Last Updated:** Thu Jan 12, 2012 06:16 PM UTC
**Owner:** IOhannes m zmölnig
If you have many \[pix\_image\] objects in a patch, even if none of them loads
any image and even if none of them is connected to any gemhead, Pd will consume
a lot of CPU, apparently proportional to the number of \[pix\_image\] instances.
On a dual core machine, the amount of CPU consumption can exceed 100% of a
core, so I guess the issue must be in some part of the code that is threaded -
hopefully this may help to track down the issue.
The attached patch \(64 pix\_images\) eats 150% of my intel core duo t9300 on
Ubuntu 10.04 while the patch is doing absolutely nothing.
This makes it impossible to have a handful of pix\_image objects with preloaded
images and dynamically choose which one to show, just to name one thing that
can't be done and which should not be resource-demanding. This kills any
project working with images.
---
Sent from sourceforge.net because [email protected] is subscribed to
https://sourceforge.net/p/pd-gem/bugs/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/pd-gem/admin/bugs/options. Or, if this is a mailing
list, you can unsubscribe from the mailing list.
_______________________________________________
GEM-dev mailing list
[email protected]
http://lists.puredata.info/listinfo/gem-dev
