macOS version doesn't use jemalloc

[ashie]

Although dmg package for macOS bundles jemalloc as same as packages for linux platforms, it doesn't use jemalloc.
To enable it, LD_PRELOAD environment variable is required. But probably no one sets it on macOS.

[ashie]

Probably we need to add EnvironmentVariables to td-agent.plist.

[kenhys]

@ashie
will you fix for 4.2.0?

[ashie]

No. I'm in final testing for 4.2.0.
It should be fixed in future version.

[cosmo0920]

FYI; td-agent 4.5.0 (or under version?) has dead lock issue on macOS.
If we use jemalloc on macOS, we might have to revert to downgrade jemalloc version.
jemalloc/jemalloc#895

[cosmo0920]

And also, we should use DYLD_LIBRARY_PATH on macOS instead of LD_LIBRARY_PATH to replace malloc implementation with jemalloc.

[ashie]

FYI; td-agent 4.5.0 (or under version?) has dead lock issue on macOS.

Thanks for the information.
Do you mean jemalloc?

- td-agent 4.5.0
+ jemalloc 4.5.0

It seems that it's affect to jemalloc 4.5.0 - 5.0.0.
<= 4.4.0 or >= 5.1.0 aren't affected.

• https://github.com/jemalloc/jemalloc/releases/tag/5.1.0
• Update jemalloc to 4.5.0 rust-lang/rust#41861
  • rust-lang/jemalloc@11bfb0d...3288e06

If we use jemalloc on macOS, we might have to revert to downgrade jemalloc version.
jemalloc/jemalloc#895

td-agent 4.2.0 includes an amazing challenge for jemalloc.
It downgrades jemalloc to 3.6.0: #305

[ashie]

And also, we should use DYLD_LIBRARY_PATH on macOS instead of LD_LIBRARY_PATH to replace malloc implementation with jemalloc.

You are right, I forgot it.
Thanks for notifying it.

[ashie]

FYI; td-agent 4.5.0 (or under version?) has dead lock issue on macOS.

BTW it might not be so critical for Ruby, because it uses Giant VM Lock.

[cosmo0920]

Thanks for the information.
Do you mean jemalloc?

Yes, I mean jemalloc.

[ashie]

It seems that it's affect to jemalloc 4.5.0 - 5.0.0.
<= 4.4.0 or >= 5.1.0 aren't affected.

  * [rust-lang/jemalloc@11bfb0d...3288e06](https://github.com/rust-lang/jemalloc/compare/11bfb0dcf85f7aa92abd30524bb1e42e18d108c6...3288e0659c08fb5006f6d6dd4b5675ed0c2c432a)

No, it bumped from 4.1.0 to 4.5.0.
So 4.1.1 - 5.0.0 are possible to be affected.

[cosmo0920]

Oh, it's widely spreaded issue...

[github-actions]

This issue has been automatically marked as stale because it has been open 90 days with no activity. Remove stale label or comment or this issue will be closed in 30 days