On Fri, Jun 8, 2018 at 12:16 PM Jon Siwek <jsi...@corelight.com> wrote:
> Only thing I'm thinking is that your test system maybe > does a poorer job of scheduling the right thread to run in order for > the FlushPendingQueries() spin-loop to actually finish. Actually, realized you still had bad timing with data stores off, so it would more likely be a problem with the AdvanceTime() code path. There's some mutex locking going on there, but w/o data stores involved there shouldn't be anyone competing for them. - Jon _______________________________________________ bro-dev mailing list bro-dev@bro.org http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
