Bug 305587 - currentSource change ought to be async
Summary: currentSource change ought to be async
Status: CONFIRMED
Alias: None
Product: Phonon
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR major
Target Milestone: 4.6.1
Assignee: Harald Sitter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-22 11:01 UTC by Harald Sitter
Modified: 2021-03-09 22:36 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Sitter 2012-08-22 11:01:28 UTC
Currently when libphonon gets an aboutToFinish from the backend it forwards it in a blocking manner to the consumer which will then be able to set the next source. upon returning of the emission it then dequeues an item and sets it as new source whilist setting it as next source for the backend.

There is a grave problem with this as the only way to know that the backend actually changed the source is when it emitted the sourceChanged signal, so ultimately currentSource would only be changed on an explicit change (setCurrentSource) or when the backend emitted aforementioned signal. In particular we do not know how much time the backend leaves between aboutToFinish and finish, in case of pgst I have seen this to be ~8 seconds, which is a long time for providing bogus information to the frontend.

Reproducible: Always
Comment 1 Harald Sitter 2012-08-22 11:01:56 UTC
also see bug #305021
Comment 2 Justin Zobel 2021-03-09 22:36:56 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.