search

TerrificInToronto / peerblock

Automatically exported from code.google.com/p/peerblock
Other
0 stars 0 forks source link

An uncaught exception occured (SQL logic error or missing database) #313

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. No step. My computer with Windows 7 x64 run with no reboots a week for
example. And exception may shows once in a week. Or once in a day.
After exception and re-run PeerBlock work normally.

What is the expected output? What do you see instead?
Its dozens opened windows with exceptions like this (from log)
Thankyou for helping us improve PeerGuardian!
[5/16/2010] [05:35:45.184] [01260]      ^^^^  EXCEPTION!!  ^^^^
[5/16/2010] [05:36:00.182] [01260]      vvvv  EXCEPTION!!  vvvv
[5/16/2010] [05:36:00.182] [01260]  An uncaught exception occured!

This problem has been automatically reported to Phoenix Labs.  The report
contains the following information:

Build Number: 40909270181
File: .\logproc.cpp
Line: 337
Type: class sqlite3x::database_error
Message: SQL logic error or missing database

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

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 1881...@gmail.com on 16 May 2010 at 4:01

Attachments:

GoogleCodeExporter commented 8 years ago 
This is Issue #230.

It is usually caused by your history.db file - the file PeerBlock uses to store 
its
history of your allowed/blocked connections - growing too large.  This file can 
be
found in C:\Program Files\PeerBlock by default; exiting PeerBlock, deleting this
file, then restarting PeerBlock should resolve the problem.  

To prevent this problem from occurring in the future, on the first page of the
PeerBlock Settings panel, under the "History" section, set it to "Remove" every 
"7"
days or so.  If you're running our Beta release there will also be an option 
called
"History size"; setting this option to something like 100 MB will prevent the
history.db file from growing too large.  (It will also be present in our 
upcoming 1.1
Stable Release, due out in a week or so.)

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

GoogleCodeExporter commented 8 years ago 
Why is showing ?

Original comment by zahir4...@gmail.com on 16 Aug 2013 at 1:32

Attachments: