Closed GoogleCodeExporter closed 9 years ago
Original comment by peerbloc...@gmail.com
on 2 Nov 2009 at 5:07
Original comment by peerbloc...@gmail.com
on 3 Nov 2009 at 8:13
I have the same problem, PB just hangs their with no indication it is still
running,
this is a problem on safe sites, not allowing them to open. The only way is to
restart your comp, then you get the error message, PB will not shut down. This
is a
real pain if you have to restart your comp to use the web for safe sites.
bardisan
Original comment by bardi...@spin.net.au
on 19 Nov 2009 at 1:13
I'm sorry to hear that you've hit this too.
While we still haven't made any progress on this one, I think you should be
able to
workaround it by going into the Task Manager (Ctrl+Shift+Escape, or right-click
on
taskbar then select Task Manager, or Ctrl+Alt+Delete then select Task Manager),
finding peerblock.exe in the Processes tab, then right-clicking on it and
selecting
"End Process Tree". This should at least force it to close so that you can
have a
chance at restarting it (and then either Allowing HTTP or else getting it to
exit
"for real").
Original comment by peerbloc...@gmail.com
on 19 Nov 2009 at 1:50
Many thanks for your reply. Sorry have tried that, PB does not show as running,
the
only way todate is to restart youe comp.
Regards Bardisan.
Original comment by bardi...@spin.net.au
on 20 Nov 2009 at 3:54
Could those of you who are able to reproduce this bug please try running this
test
version?
http://update.peerblock.com/bugs/i152_js3j0/PeerBlock-Setup_v1.0+_r305.exe
This version has some additional tracelogging in it around this problem area,
so if
you can reproduce the problem with it and upload your peerblock.log file that
should
help us chase down the root cause of this problem. This version has a bunch of
new
stuff in it as compared to the most recent Beta Release, but nothing too
destabilizing I don't think. It is built as a Beta Release though which means
that
it will detect the next Beta Release once one is released.
Original comment by peerbloc...@gmail.com
on 1 Mar 2010 at 6:18
Two weeks with no feedback about the latest additional-debug-information build I
posted, so at this point I'm going to assume that nobody's seeing this problem
anymore. The additional debug info code is also in our most recent Beta
Release, so
if anyone hits this problem in the future we can get that info.
Closing this bug for now, we can re-open it if someone reproduces it and is
able to
get us the additional info we need to make progress.
Original comment by peerbloc...@gmail.com
on 16 Mar 2010 at 3:01
Original issue reported on code.google.com by
peerbloc...@gmail.com
on 2 Nov 2009 at 5:07