OK, but if this scenario was at the origin of my problem, I guess I would
have such a log each time a db query freezes ?

If yes, then there is probably another problem, as I am sure I got such
freezes with no such logs from sqlite.

By the way, if the antivirus is at the origin of the problem, which
practical solution may I find to the problem ? I cannot request my client
to deactivate his antivirus. And he is using a very common one (norton).
So, I would probably not be the only one to have this problem ?

Is there a way to request SQlite to don't release control of the file
between two operations ? As I only open one descriptor, this could maybe
help if it was possible ? Maybe I could ask sqlite to take control of the
file at the beginning of my program, and request it to release control at
the end ?

Thanks for your help,

Regards,

Brice

2015-11-09 17:26 GMT+01:00 Richard Hipp <drh at sqlite.org>:

> So the problem is occurring on a call to GetFileAttributesEx().
>
> I'm guessing that this is an adverse interaction with an anti-virus
> (AV) program.
>
> The scenario might be something like this.
>
> (1) SQLite writes one small part of a complex change to the database file
> (2) The AV seizes control and scans the entire database, taking a long
> time to do so (because the file is large) and denying SQLite access
> while it does.
> (3) The AV finally releases control of the file
> (4) Goto 1.
>
>
> On 11/9/15, Brice Andr? <brice.andre at ams-solutions.be> wrote:
> > Dear Richard,
> >
> > Thanks for your answer. The version of sqlite I am using is the 3.9.1
> > amalgamation.
> >
> > But, as stated above, I am not sure my freeze problem is linked to the
> > strange log observed at my client as this log does not systematically
> > appears on database queries that freeze. Those logs sometimes appear on
> > queries that do not freeze, and sometimes, queries that freeze do not
> have
> > those logs.
> >
> > I checked in the different logs I have collected, and it seems to be
> always
> > the same line (39428) that causes this strange log.
> >
> > Regards,
> >
> > Brice
> >
> > 2015-11-09 16:36 GMT+01:00 Richard Hipp <drh at sqlite.org>:
> >
> >> On 11/9/15, Brice Andr? <brice.andre at ams-solutions.be> wrote:
> >> >
> >> > 08-11-2015 (13h25): Exception: SQLiteDataBase : Error callback -> 27 :
> >> > delayed 25ms for lock/sharing conflict at line 39428
> >>
> >> The "line 39428" refers to a specific source code line number in the
> >> "sqlite3.c" file, which in turn depends on exactly which version of
> >> SQLite you are running - information which you failed to share with
> >> us.  If you will let us know which version of SQLite you are running,
> >> we might be able to figure out what is going wrong.
> >> --
> >> D. Richard Hipp
> >> drh at sqlite.org
> >> _______________________________________________
> >> sqlite-users mailing list
> >> sqlite-users at mailinglists.sqlite.org
> >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >>
> > _______________________________________________
> > sqlite-users mailing list
> > sqlite-users at mailinglists.sqlite.org
> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >
>
>
> --
> D. Richard Hipp
> drh at sqlite.org
> _______________________________________________
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

Reply via email to