Because every possible query that can be run on the server has been tested and the CPU problem happens randomly.


----- Original Message ----
From: Ivan Prenosil <Ivan.Prenosil@...>
To: firebird-support@yahoogroups.com
Sent: Wednesday, January 3, 2007 11:22:22 AM
Subject: Re: [firebird-support] Re: Terminate Long Running Transaction

>I have been debugging the application for several weeks now and have not had any luck trapping the leak because it is extermely
>hard to reproduce.
>
> The reason I kow it is caused by the garbage collector is because I posted an inquiry in this newsgroup long ago about an issue
> where fbserver.exe was pegging the CPU on my server (Firebird v2). The conclusion was that the garbage collector was responsible
> for that behavior. When I reverted back to 1.5.3, the server works just fine.

I have read that thread, and have not found any concrete/useful informations,
nor anything indicating that garbage collection is really the problem.

Most probably the difference is that FB2 chooses bad plan for some
specific query. Why do you think this is not the case ?

Ivan




[Non-text portions of this message have been removed]