fluent
diff --git a/‎lib/Fluent/Logger.pm
Copy file name to clipboardExpand all lines: lib/Fluent/Logger.pm
+2Lines changed: 2 additions & 0 deletions b/‎lib/Fluent/Logger.pm
Copy file name to clipboardExpand all lines: lib/Fluent/Logger.pm
+2Lines changed: 2 additions & 0 deletions
diff --git a/‎t/09_buffer_overflow_handler.t
Copy file name to clipboardExpand all lines: t/09_buffer_overflow_handler.t
+3-2Lines changed: 3 additions & 2 deletions b/‎t/09_buffer_overflow_handler.t
Copy file name to clipboardExpand all lines: t/09_buffer_overflow_handler.t
+3-2Lines changed: 3 additions & 2 deletions
@@ -140,6 +140,7 @@ sub close {
         if ($@ || !$written) {
             my $size = length $self->{pending};
             $self->_carp("Can't send pending data. LOST $size bytes.: $@");
+            $self->_call_buffer_overflow_handler();
         }
         else {
             $self->_carp("pending data was flushed successfully");
@@ -341,6 +342,7 @@ You can inject your own custom coderef to handle buffer overflow in the event of
 This will mitigate the loss of data instead of simply throwing data away.
 
 Your proc should accept a single argument, which will be the internal buffer of messages from the logger.
+This coderef is also called when logger.close() failed to flush the remaining internal buffer of messages.
 A typical use-case for this would be writing to disk or possibly writing to Redis.
 
 =item truncate_buffer_at_overflow
 
@@ -18,9 +18,10 @@ my $no_such_logger = Fluent::Logger->new(
 for (1..10) {
     $no_such_logger->post("test", { "k" => "v" x (1024 * 1024) });
 }
-undef $no_such_logger;
+is $handler_called, 1, 'called once at buffer_overflow';
 
-is $handler_called, 1;
+undef $no_such_logger;
+is $handler_called, 2, 'called once at close';
 
 done_testing;