Closed GoogleCodeExporter closed 9 years ago
It's reproducible.
Appears that the pgfilter_base::setblockhttp is called from 2 threads (1 UI, 1
not) and it caused a deadlock. Patch
removes the mutex from that method. Also removes the mutex from the
pgfilter_base::setblock for the same reason.
Doesn't look like there's any side effect of removing the mutex except that
during heavy blocks, it will still
allow/block for a bit of time after pressing the button. Possibly related to
the pgfilter internal queue.
Original comment by nightstalkerz
on 5 Sep 2009 at 8:02
Attachments:
Additional discussion taking place on the Dev Team forum; I think we may want to
create new mutexes instead of removing them from this code entirely.
From early tests, looks like this fix may also resolve Issue 21 and Issue 82.
Original comment by peerbloc...@gmail.com
on 8 Sep 2009 at 11:56
Original comment by peerbloc...@gmail.com
on 8 Sep 2009 at 11:58
Original comment by peerbloc...@gmail.com
on 8 Sep 2009 at 11:58
[deleted comment]
Original comment by peerbloc...@gmail.com
on 10 Sep 2009 at 1:39
This issue was closed by revision r137.
Original comment by peerbloc...@gmail.com
on 10 Sep 2009 at 2:12
Issue 21 has been merged into this issue.
Original comment by peerbloc...@gmail.com
on 10 Sep 2009 at 2:14
Issue 82 has been merged into this issue.
Original comment by peerbloc...@gmail.com
on 10 Sep 2009 at 2:14
Issue 125 has been merged into this issue.
Original comment by peerbloc...@gmail.com
on 26 Sep 2009 at 8:19
Original issue reported on code.google.com by
Praese...@gmail.com
on 30 Aug 2009 at 5:33Attachments: