Incorrect use of g_cond

Bug #1227542 reported by Paweł Stołowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mediascanner
Fix Released
High
Jussi Pakkanen
mediascanner (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

g_cond is not used correctly, e.g. in this code

if (not is_idle()) {
        g_cond_wait(&d->cond_, &d->mutex_);
...

According to the docs, it must be used in a loop to avoid spurious wakeups.

Related branches

Changed in mediascanner:
assignee: nobody → Jussi Pakkanen (jpakkane)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mediascanner at revision 385, scheduled for release in mediascanner, milestone Unknown

Changed in mediascanner:
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mediascanner - 0.3.93+13.10.20130919.2-0ubuntu1

---------------
mediascanner (0.3.93+13.10.20130919.2-0ubuntu1) saucy; urgency=low

  [ Jussi Pakkanen ]
  * Fix usage of GCond. (LP: #1227542)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 385
 -- Ubuntu daily release <email address hidden> Thu, 19 Sep 2013 23:08:20 +0000

Changed in mediascanner (Ubuntu):
status: New → Fix Released
Michal Hruby (mhr3)
Changed in mediascanner:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.