Upgrading from glib 2.78.3 to 2.78.4 introduced regression

[viralmutant]

Output of brew config

HOMEBREW_VERSION: 4.2.7
ORIGIN: https://github.com/Homebrew/brew
HEAD: 6170b6297c61ef0b68814c708eeff2199d8b0d11
Last commit: 3 days ago
Core tap JSON: 08 Feb 11:23 UTC
Core cask tap JSON: 08 Feb 11:23 UTC
HOMEBREW_PREFIX: /opt/homebrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 4
HOMEBREW_SORBET_RUNTIME: set
Homebrew Ruby: 3.1.4 => /opt/homebrew/Library/Homebrew/vendor/portable-ruby/3.1.4/bin/ruby
CPU: quad-core 64-bit dunno
Clang: 15.0.0 build 1500
Git: 2.39.3 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 8.1.2 => /usr/bin/curl
macOS: 13.5.2-arm64
CLT: 15.0.0.0.1.1694021235
Xcode: N/A
Rosetta 2: false

Output of brew doctor

Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: A newer Command Line Tools release is available.
Update them from Software Update in System Settings.

If that doesn't show you any updates, run:
  sudo rm -rf /Library/Developer/CommandLineTools
  sudo xcode-select --install

Alternatively, manually download them from:
  https://developer.apple.com/download/all/.
You should download the Command Line Tools for Xcode 15.1.


Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
  openssl@1.1

Warning: Some taps are not on the default git origin branch and may not receive
updates. If this is a surprise to you, check out the default branch with:
  git -C $(brew --repo ****/glib) checkout

Description of issue

I am building Samba on Mac OsX 13.5.2, M1 chip.
Samba build was successful and running fine until I upgraded glib from v2.78.3 to v2.78.4. Note that I didn't make any changes to Samba.

Now trying to run Samba gives this message along with a backtrace

objc[1019]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called.
objc[1019]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.

Googling suggested using an additional env. variable OBJC_DISABLE_INITIALIZE_FORK_SAFETY=yes, but I wanted to understand what changed across versions. Is this something expected or a regression ?

[e40]

I have a variation of this:

mini18:~ admin$ command-does-not-exist
objc[60657]: +[Swift.__SharedStringStorage initialize] may have been in progress in another thread when fork() was called.
objc[60657]: +[Swift.__SharedStringStorage initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
Abort trap: 6
mini18:~ admin$ 

The OBJC_DISABLE_INITIALIZE_FORK_SAFETY=yes hack did not change the output.