Bug #625

events dropped count misses events since 2.3

Added by Mathieu Desnoyers almost 7 years ago. Updated over 6 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Since 2.3, test_high_throughput_limits validation fails due to missing event dropped.

Further testing indicates that all recorded events are present in the trace (tried modifying the ring buffer to retry writing events on failure), and the total of events dropped as seen by the consumerd does not match the final result shown by babeltrace. It does not seem to be a babeltrace issue, since it works correctly with stable-2.2. Finally, babeltrace shows that 0 events are dropped at the end of each stream (not sure if relevant, could be normal).

Since this does not affect events recorded, this is not a release blocker, but we should look into this issue.

Related issues

Related to Babeltrace - Bug #589: Lost events time ranges may be offsetResolvedMathieu Desnoyers07/09/2013


Updated by Mathieu Desnoyers over 6 years ago

  • Target version set to 2.4

Updated by Mathieu Desnoyers over 6 years ago

  • Target version changed from 2.4 to 2.3

Updated by Mathieu Desnoyers over 6 years ago

  • Project changed from LTTng-UST to Babeltrace
  • Status changed from New to In Progress

This is a babeltrace issue.


Updated by Mathieu Desnoyers over 6 years ago

  • Status changed from In Progress to Resolved

Fixed by babeltrace commit:

commit 2654fe9bab8f0eaeb17264ef7abadfd14e245b23
Author: Mathieu Desnoyers <>
Date:   Tue Feb 25 17:36:11 2014 -0500

    Fix: events discarded timing inaccuracy

    Introduce babeltrace_ctf_console_output too, to ensure we only print
    discarded events when a text output is used.

    Fixes #589

    Signed-off-by: Mathieu Desnoyers <>

Also available in: Atom PDF