<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Coroutines may be messing up with GTask's return"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94662">94662</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Coroutines may be messing up with GTask's return
</td>
</tr>
<tr>
<th>Product</th>
<td>Spice
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>spice-gtk
</td>
</tr>
<tr>
<th>Assignee</th>
<td>spice-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>fabiano@fidencio.org
</td>
</tr></table>
<p>
<div>
<pre>I've seen some weird behaviors of the GTask returning immediately when it was
supposed to return in idle, in spice-gtk code.
What I got from a brief talk with Dan Winship is that "a GTask will return
immediately only if:
(a) it is in a thread which is running the GMainContext that the task was
started in, and (b) that GMainContext has run at least one iteration since the
thread started (...) So if you have tasks that are returning immediately when
they shouldn't be, figure out how it is that those conditions are coming to be
true when you don't expect them to be)".
And that "If you are doing things like messing with the stack or calling
setcontext(), then it's possible that could mess things up. I don't know."
Let's investigate how to fix the coroutines on our side and, later on, open a
bug on GLib as well if that's the case.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>