From: stefano.tortarolo@... Date: 2015-07-10T15:36:18+00:00 Subject: [ruby-core:69940] [Ruby trunk - Bug #9115] Logger traps all exceptions; breaks Timeout Issue #9115 has been updated by Stefano Tortarolo. I confirm that this bug is reproducible up to 2.2 and it's pretty easy to trigger. ~~~ require 'timeout' require 'logger' class MyExc < RuntimeError; end def long_call(logger) Timeout.timeout(3, MyExc) do a = 1 loop do a += 1 logger.warn "Test #{a}" end end end ~~~ Aaron Stone is right though that using 2.1+ it would work if you don't provide a custom exception or if your exception inherits from TimeoutError. Beware that it must inherit from Object::TimeoutError and not Timeout::Error. Having said that, it'd be nice to have a proper fix at logger.rb level. @Bill, I don't think your code would fix it though, because the underlying device might throw a different exception. ---------------------------------------- Bug #9115: Logger traps all exceptions; breaks Timeout https://bugs.ruby-lang.org/issues/9115#change-53367 * Author: Chris Phoenix * Status: Open * Priority: Normal * Assignee: * ruby -v: ruby 2.0.0p247 (2013-06-27) [i386-mingw32] * Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN ---------------------------------------- Line 577-579 of logger.rb rescue Exception => ignored warn("log writing failed. #{ignored}") end Thus, when the system times out in the middle of writing a log message, it warns "log writing failed. execution expired" and just keeps right on running. This is true in 1.9.3 as well. I haven't looked at older versions. Pardon me while I go grep "rescue Exception" in the entire Ruby codebase, and see whether I can reliably use Timeout at all... OK, you might check out C:\Ruby200\lib\ruby\gems\2.0.0\gems\activerecord-3.2.13\lib\active_record\railties\databases.rake All the other "rescue Exception" seem to re-raise it, except maybe C:\Ruby200\lib\ruby\2.0.0\xmlrpc\server.rb and C:\Ruby200\lib\ruby\gems\2.0.0\gems\activesupport-3.2.13\lib\active_support\callbacks.rb -- https://bugs.ruby-lang.org/