On 04/21/2016 12:47 PM, Thomas Steinmaurer wrote: > Hi Alex, > >>>> Hello Vlad, >>>> >>>>>> 20.04.2016 0:47, Thomas Steinmaurer wrote: >>>>>> ... >>>>>>> What else could I provide so that you can investigate the offending >>>>>>> thread? >>>>>> Full memory dump, please. >>>> Have you had time to look at it? >>>> >>>> Unfortunately this now also has happened in a production environment at >>>> a customer site. >>>> >>>> We did quite some testing in the trace area at Firebird 3 Alpha stage >>>> and I can't remember any troubles there (in hope my memory serves me >>>> well). So I will move back from Final to Alpha2 in a test environment >>>> and see what happens. >>> Seems to be something introduced with RC1 or possibly some sort of >>> incompatibility with (Delphi) client components using the Trace API? >>> >>> Beta2 (Firebird-3.0.0.31896-0_Win32_Beta2) seems to be fine and does not >>> show >>> the symptom of fully utilizing a single core. >>> >> Looks like I've found a reason. Thomas, are you using isc_info_svc_line >> or isc_info_svc_to_eof when reading service output? > I'm pretty sure the used third-party Delphi component does, but that's the > common way to read service output, right?
Certainly, but what particular of this two SPB parameters is used? ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
