[#97678] [Ruby master Feature#16752] :private param for const_set — bughitgithub@...
Issue #16752 has been reported by bughit (bug hit).
5 messages
2020/04/02
[ruby-core:97924] [Ruby master Bug#16793] [BUG] object allocation during garbage collection phase
From:
merch-redmine@...
Date:
2020-04-16 16:23:31 UTC
List:
ruby-core #97924
Issue #16793 has been updated by jeremyevans0 (Jeremy Evans). Status changed from Open to Third Party's Issue Based on the error message and control frame info, it appears puma is allocating an object during garbage collection, which would be a bug in puma. Try upgrading to puma 4.3.3 (the latest release), and if you still have the same issue, you probably want to contact the puma developers on GitHub: https://github.com/puma/puma/issues ---------------------------------------- Bug #16793: [BUG] object allocation during garbage collection phase https://bugs.ruby-lang.org/issues/16793#change-85147 * Author: FreddieFrog (Fr馘駻ic Champreux) * Status: Third Party's Issue * Priority: Normal * ruby -v: ruby 2.6.5p114 (2019-10-01 revision 67812) [x64-mingw32] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- Hi Our Puma server periodically stops working, and returns to command line without error message. Nothing has changed to the configuration, but today, for the first time, the attached message was raised. I hope this is a good clue! Best regards, Fred ---Files-------------------------------- log1.txt (346 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>