Uncaught Exception splite3 database error

[GoogleCodeExporter]

What steps will reproduce the problem?
1.letting the computer idle? (not even sleep)
2.2Popups appeared that said "Uncaught Exception" 
3.

What is the expected output? What do you see instead?
Not getting the popups, them. I will provide a screenshot.

What version of PeerBlock are you using? On what operating system? 32- or
64-bit? 32bit Windows 7

Please provide any additional information below.  Make sure to attach
peerblock.log and/or any screenshots that would help explain your problem.

Original issue reported on code.google.com by mikel52588 on 20 Dec 2009 at 8:06

• Merged into: #162

Attachments:

• [peerblock uncaught exception.jpg](https://storage.googleapis.com/google-code-attachments/peerblock/issue-230/comment-0/peerblock uncaught exception.jpg)

[GoogleCodeExporter]

Again last night I received the same message after being away from my computer 
for a
while (two of them again). So it must have something to do with the computer 
idling 

Original comment by mikel52588 on 21 Dec 2009 at 4:20

[GoogleCodeExporter]

These sqlite "Disk I/O Errors" are pretty hard to figure out actually - they're
reported to us by the third-party code we use to write out your history to a 
logfile
(history.db), and basically mask the OS-specific error causing the problem. 
Supposedly these errors may be indicative of a failing disk, so I would 
recommend
running chkdsk and/or some other low-level diagnostics tool specific to your
harddrive to make sure it's good.  

Barring any problems found there, since we really have no way of understanding 
what's
happening underneath the covers here, there are a couple of things you could 
try. 
The first would be to stop PeerBlock, then rename your history.db file and let
PeerBlock recreate it when you restart it.  If the file was sitting on a bad 
block or
something this should help with that.  

If after that you continue seeing the errors, you can go into your PeerBlock 
Settings
and change the leftmost dropdown box in the History section to be "Log None".  
This
will completely prevent PeerBlock from using the third-party code that's giving 
us
this error, but will also mean that you'll have no history other than what 
shows up
in your main PeerBlock display.

Good luck, and please let us know how things end up working out!

Original comment by peerbloc...@gmail.com on 21 Dec 2009 at 5:03

[GoogleCodeExporter]

Ok yea I'll do some of the stuff you suggested. I also got a .dmp file that for 
some
reason I just noticed even though it was on my desktop. I'm going to attach it, 
maybe
it can give some insight. 

Original comment by mikel52588 on 21 Dec 2009 at 5:23

Attachments:

• peerblock.dmp

[GoogleCodeExporter]

So just a quick update. I use diskeeper which is awesome, but it wasn't turned 
on
because another program was blocking it; therefore, my disk had like 25,000 
fragments
all created in the past few days. Very likely to be the problem. Thank you for
pointing that out. I hope that fixes the prob. I'll update if I have anything 
else to
share.

Original comment by mikel52588 on 21 Dec 2009 at 11:28

[GoogleCodeExporter]

Sounds like the aforementioned workarounds are resolving the problem for 
people, so
what we should do here is trap this error and minimally present a better error
message explaining the problem and what people can do about it, and potentially 
offer
to try deleting/recreating the history.db file for people.

Marking as targetted for 1.1, since quite a few people have been reporting this 
of late.

Original comment by peerbloc...@gmail.com on 31 Dec 2009 at 4:41

• Changed state: Accepted
• Added labels: Milestone-1.1

[GoogleCodeExporter]

I had this problem... I went to the history.db file and saw it was 2.7 GB! 
Removed
it... set to LOG NONE... everything works perfectly now! That issue was causing 
my
Windows7 to BLUE SCREEN before figuring this out... BAD TIMES!

Original comment by gregpete...@gmail.com on 26 Feb 2010 at 3:46

[GoogleCodeExporter]

Same issue as gregpetersen.  Some other items to note:

1. I'm running Peerblock on a WHS machine.  I am able to easily reproduce this 
error 
if logging into the server via RDP as a different user than the one that 
originally 
launched Peerblock.

2. I also had the history.db issue.  Not sure if related to #1, but earlier 
comments 
caught my eye.

Original comment by michael....@gmail.com on 16 Apr 2010 at 4:14

[GoogleCodeExporter]

Issue 313 has been merged into this issue.

Original comment by peerbloc...@gmail.com on 16 May 2010 at 5:45

[GoogleCodeExporter]

Original comment by nightstalkerz on 29 Sep 2010 at 9:03

• Changed state: Duplicate