Summary: | Coroutines may be messing up with GTask's return | ||
---|---|---|---|
Product: | Spice | Reporter: | Fabiano FidĂȘncio <fabiano> |
Component: | spice-gtk | Assignee: | Spice Bug List <spice-bugs> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Fabiano FidĂȘncio
2016-03-22 18:51:31 UTC
No conflict for me, the task GMainContext is the same (there is no thread etc). It makes sense that there has been further main loop iteration before the task returns. spicevmc want to return in idle, so the caller resumes in "main" coroutine context. I don't know what happens if you do the task return from the coroutine. Most likely, this ends in laster coroutine yields errors if the resume function do not deal well with coroutine contexts. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/spice/spice-gtk/issues/4. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.