Goom visualization is unusable at 'Normal' size and higher
Bug #41707 reported by
Vytas
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| GStreamer |
Fix Released
|
Medium
|
|||
| gst-plugins-good0.10 (Ubuntu) |
Fix Released
|
Low
|
Ubuntu Desktop Bugs | ||
Bug Description
Goom visualization works as expected as 'Small' size. But if I increase it to 'Normal', 'Large' or 'Extra Large', totem sucks up 1 CPU to 100% (I use P4 HT), and the sound output becomes choppy or no output at all. Visualization is invisible too.
However, sometimes it is possible to restore it to working normally by dragging the possition slider, pausing/unpausing etc. Then CPU usage drops back to ~10% on 'Normal' size, ~25% on Large size (average from both virtual processors). So CPU it is capable of doing those Gooms at realtime, the problems lie somewhere else.
Im not sure, but IIRC it is a regression from Flight5-6 where it worked fine.
I attach the part of GST_DEBUG=3 totem output.
Revision history for this message
| Vytas (vytas) wrote Totem, goom with 'Normal' size | #1 |
Revision history for this message
| Sebastien Bacher (seb128) wrote | #2 |
| Changed in gst-plugins-good0.10: | |
| assignee: | nobody → desktop-bugs |
| status: | Unconfirmed → Confirmed |
Revision history for this message
| Sebastien Bacher (seb128) wrote | #3 |
| Changed in gst-plugins-good0.10: | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Sebastian Dröge (slomo) wrote | #4 |
| Changed in gst-plugins-good0.10: | |
| status: | Fix Committed → Fix Released |
| Changed in gstreamer: | |
| importance: | Unknown → Medium |
To post a comment you must log in.
No special information here though, just warnings like
WARN (0x8504118 - 0:00:06.240627000) mad( 9806) gstmad.