Bug #21173: RUBY_FREE_AT_EXIT does not work when error in -r

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONE

[peterzhu2118 (Peter Zhu)]

PR: https://github.com/ruby/ruby/pull/12859

When loading a file using the command line -r, it is processed before RUBY_FREE_AT_EXIT is checked. So if the loaded file raises an error, it will cause memory to not be freed with RUBY_FREE_AT_EXIT.

For example ruby -rtest.rb -e "" will report a large amount of memory leaks if test.rb raises.

[peterzhu2118 (Peter Zhu)]

• Status changed from Open to Closed

Applied in changeset git|6bad47ac6d62b54fe30e3f161c2a9d8f5fa4800c.

---

RUBY_FREE_AT_EXIT does not work when error in -r

[Bug #21173]

When loading a file using the command line -r, it is processed before
RUBY_FREE_AT_EXIT is checked. So if the loaded file raises an error, it
will cause memory to not be freed with RUBY_FREE_AT_EXIT.

For example ruby -rtest.rb -e "" will report a large amount of memory
leaks if test.rb raises.

[tenderlovemaking (Aaron Patterson)]

• Backport changed from 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: REQUIRED to 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONE

Backported in 762e76cc50db059e71d1f6c13674103a488f5171