Opened 8 years ago

Closed 7 years ago

#2879 closed bug (Fixed)

Opening a file from a finished torrent causes a dyld error

Reported by: Lord-Kamina Owned by:
Priority: major Milestone: 1.3.14
Component: Packaging Version: 1.3.13
Keywords: dyld, environment, lib Cc:


I just noticed this bug, which appears to be present at least since 1.3.12 (haven't tested with prior versions) in OSX.

If you try to open a file from inside a finished torrent, occasionally you get a dyld error because for some reason whichever app tries to load with DYLD_LIBRARY_PATH=/Applications/Deluge?.app/Contents/Resources/lib

Change History (5)

comment:1 Changed 7 years ago by Cas

I cannot replicate on my osx virtualbox. Do you have a specific file type and application?

Does it work if you modify /Applications/

- export DYLD_LIBRARY_PATH = $bundle_lib

comment:2 follow-up: Changed 7 years ago by Cas

  • Milestone changed from needs verified to 1.3.14

comment:3 in reply to: ↑ 2 Changed 7 years ago by Lord-Kamina

Nope, that doesn't fix it. Although I think I have some more info on the particular circumstances that might trigger the bug.

It doesn't occur with everything, I was originally (and am still) seeing it when trying to open a video that would launch, and I noticed the particular error is caused by mpv trying to use libfreetype and instead finding's own libfreetype (which is an earlier, thus deemed incompatible, version)

Obviously the root of the issue would appear to be the same thing; for some reason it is trying to launch with its own DYLD_LIBRARY_PATH.

I attempted both the fix you suggested and also inverting $bundle_lib and $DYLD_LIBRARY_PATH but $DYLD_LIBRARY_PATH is empty at that point in the script so it's the same as doing nothing.

Tampering around with your idea though; I HAVE found a fix, although I don't know if it will have any ramificatons.

- export DYLD_LIBRARY_PATH = $bundle_lib
+ export DYLD_FALLBACK_LIBRARY_PATH = $bundle_lib

comment:4 Changed 7 years ago by Cas

Thanks that is a useful update. We might have to just go with that as I am not entirely sure atm what the correct way to do this is.

This might explain why modifying DYLD_LIBRARY_PATH didn't work if it contains an absolute path:

OSX is such a headache... do you feel like switching to Ubuntu? ;)

comment:5 Changed 7 years ago by Cas

  • Resolution set to Fixed
  • Status changed from new to closed

Fixed 1.3-stable [7f01dc909] develop [011afe3e8]

Note: See TracTickets for help on using tickets.