[OS X 10.9] dyld: Symbol not found: _pthread_chdir_np

[RJVB]

FF Dynasty 132.0 seemed to work fine for me in quick testing, so I set it up to run on a clone of the profile I use in Waterfox (G3.2.7-osxfix-eol).

It starts up OK, opening all the windows it should that even look like they do in Waterfox, but then it hangs after I've just been able to cancel the "make default browser" invitation. Launching from a terminal I see

> /path/to/FFDynasty-1320/Firefox.app/Contents/MacOS/firefox
_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
2024-10-28 00:02:51.466 firefox[11376:10d03] CoreText performance note: Client called CTFontCreateWithName() using name "Lucida Grande" and got font with PostScript name "LucidaGrande". For best performance, only use PostScript names when calling this API.
2024-10-28 00:02:51.467 firefox[11376:10d03] CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
[GFX1]: NextSurface returning false because of invalid mSize (0, 0).
_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
console.error: "attribute_timeout: attachedFxAOAuthClients"
console.error: (new Error("attachedFxAOAuthClients targeting getter timed out after 5000ms", "resource://messaging-system/targeting/Targeting.sys.mjs", 139))
JavaScript warning: moz-extension://a4d71339-e05c-a94f-84ab-921ad5ea5077/js/Driver/Bookmarks.js, line 1642: unreachable code after return statement
dyld: lazy symbol binding failed: Symbol not found: _pthread_chdir_np
  Referenced from: /path/to/FFDynasty-1320/Firefox.app/Contents/MacOS/XUL
  Expected in: /usr/lib/libSystem.B.dylib

dyld: Symbol not found: _pthread_chdir_np
  Referenced from: /path/to/FFDynasty-1320/Firefox.app/Contents/MacOS/XUL
  Expected in: /usr/lib/libSystem.B.dylib

_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.

It seems quite likely that the attempted use of pthread_chdir_np() is the culprit here; they appear just before the beachball A bit strange that FF wouldn't be prepared to handle XUL crashes though...

[RJVB]

FWIW, re: pthread_[f]chdir_np():

the Chromium source indicates that this concept exists since 10.5, but you have to use the syscall directly.