CPU load and grilo requests
Submitted by Lionel Landwerlin
Assigned to gri..@..e.bugs
When running an application rendering a UI at a fixed frame rate (like 60fps), you might end up always having something to do in the main loop at all time. In that case you will see the requests you make through the grilo API block forever. This is due to the usage of g_idle_add*() functions in the core.
This might be worked around by replacing all g_idle_add* calls by g_timeout_add(0, ...), so we ensure to return to the caller as soon as possible, but we also ensure that the plugin's callback will be called at some point (and not delayed forever).
Another way to do that would be to run all plugins in another thread (only 1 thread for all plugins) separated from the caller's thread. The grilo API would then just be a kind of proxy to internal sources callbacks.
Version: git master