Memory leak with MultiJSON.dump

[sethboyles]

In a Rails app serving JSON responses, we noticed the following memory leak:

allocated by memory (61079397) (in bytes)
==============================
  61079397  /var/vcap/data/packages/cloud_controller_ng/46a8cc86e43a32e41d5b5e91e6983e75542ed547/gem_home/ruby/3.1.0/gems/multi_json-1.15.0/lib/multi_json/adapters/oj.rb:56

object count (1)
==============================
  1  /var/vcap/data/packages/cloud_controller_ng/46a8cc86e43a32e41d5b5e91e6983e75542ed547/gem_home/ruby/3.1.0/gems/multi_json-1.15.0/lib/multi_json/adapters/oj.rb:56

Memory would not be freed when the request ended, and eventually we would have to restart our process. We noticed the same behavior when using yajl.

Bypassing MultiJSON entirely resolved the issue for us.

More details here: cloudfoundry/capi-release#262 (comment)

[rwz]

This is unfortunate. Both Oj and yajl are native extensions written in C, so there's not much MultiJSON can do about it here.

I recommend switching to a different adapter or stop using MultiJSON altogether as an option to remediate memory leaks.

[sethboyles]

Well I think the memory leak is only in MultiJSON, to clarify. Using OJ.dump seems fine. It's only when using Oj via MultiJSON that we witness the memory leak. Sorry if that wasn't clear.

[sferik]

@sethboyles Can you confirm whether this still occurs in the latest version of MultiJSON?