Project

General

Profile

Actions
Copy link

Bug #16793

closed

[BUG] object allocation during garbage collection phase

Added by FreddieFrog (Frédéric Champreux) about 4 years ago. Updated about 4 years ago.

Status:
Third Party's Issue
Assignee:
-
Target version:
-
ruby -v:
ruby 2.6.5p114 (2019-10-01 revision 67812) [x64-mingw32]
Backport:
2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN
[ruby-core:97917]

Description

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) log1.txt Copy of incident raised in Windows CLI FreddieFrog (Frédéric Champreux), 04/16/2020 11:48 AM
Actions
Copy link
 #1 [ruby-core:97924]

Updated by jeremyevans0 (Jeremy Evans) about 4 years ago

  • 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

Actions
Copy link

Also available in: Atom PDF

Like0
Like0