-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
10.13.6- not launching at all #11
Comments
You already have another Firefox in the Dock? You can only have one version running at a time. |
Have tried it otherwise as well. Doesn't work. Is deleting the existing firefox and replacing it a solution? |
I'm using Firefox 115 ESR in my 10.13 Parallels VM, which is the only place I can now stream video apart from BBC iPlayer (in Mavericks using Chromium Legacy). You might find that substituting FF 115 with this one brings the same streaming problem as this legacy version hasn't (yet) incorporated the latest Widevine? |
i've had this issue too on my machine, and i think it's related to SIP but i can't say for sure. i do know i had this problem though, and it felt impossible to fix. but at that time i did notice i had SIP enabled for some reason, and disabling it seemed to fix it. try to clear the ~/Library/Caches folder as well. i think it's because the app is technically 'officially branded' but not signed by a designated developer, and sometimes this trips things up. i have no other explanation for how or why this occurs. i do know it happened to me when i restored from a time machine backup and/or reinstalled OS X |
^ Oh, that makes me think, another thing to try would be cleaning out the LaunchServices cache:
|
Can confirm similar behaviour with a couple of recent releases. MBP 8,1, macOS 10.13.6, SIP enabled/disabled, tried both workarounds mentioned here. Maybe I can help with some diagnostic data? |
Some people on MacRumors appear to have had success running the binary directly. Ctrl+Click on Firefox.app and select "Show Package Contents", then navigate to Contents/MacOS and double click the file called "firefox". The app should start up. Strangely, the MacRumors users for whom this worked say that after doing this once, Firefox could also be opened normally! Please report back! |
i think another workaround is to run the binary from another location, too.
but the bigger issue is reproducing the exact circumstances in which this issue arises.
for me, it was upon a reinstall of the same OS and/or after runnign time machine.
i wish i had concrete steps (funny coming from me, a supposed ‘maintainer’, i know) because i like tackling stupid shit like this.
…
On Oct 23, 2024, at 6:45 PM, Jonathan ***@***.***> wrote:
Some people on MacRumors appear to have had success running the binary directly. Ctrl+Click on Firefox.app → Show Package Contents and navigate to Contents/MacOS and double click the file called "firefox". The app should start up.
Strangely, the MacRumors users for whom this worked say that after doing this once, Firefox could also be opened normally!
Please report back!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Okay, fresh 10.13 Virtual Machine. Firefox 133a01 was downloaded from Github via the preinstalled Safari 11.1.2. I right click Firefox.app and select This was the part where I was hoping I could use the method I described in my last post to make Firefox work. Unfortunately, starting the binary directly doesn't seem to help in my VM. Terminal displays:
It never displays anything after this. |
it’s weird. the only thing i can think of is the rlbox libsoundtouch change but i’m reverting it in the next push (sorry big g @glandium you know i love you) because it’s a potential source of error.
even though it’s in spirit the same, libsoundtouch will go back to libxul, as it should be for anything that relies on a static rwlock.
Thanks,
Gagan
… On Oct 23, 2024, at 7:09 PM, Jonathan ***@***.***> wrote:
Okay, fresh 10.13 Virtual Machine.
Firefox 133a01 was downloaded from Github via the preinstalled Safari 11.1.2.
I right click Firefox.app and select open to bypass Gatekeeper (this is a fresh VM, so Gatekeeper is enabled). I confirm that I want to run an app from an unidentified developer. Firefox behavior matches the video in the first post. Ditto when I force quit and open it again.
This was the part where I was hoping I could use the method I described in my last post to make Firefox work. Unfortunately, starting the binary directly doesn't seem to help in my VM. Terminal displays:
Last login: Wed Oct 23 21:03:41 on ttys000
/Users/jonathan/Downloads/133a01/Firefox.app/Contents/MacOS/firefox ; exit;
Jonathans-Mac:~ jonathan$ /Users/jonathan/Downloads/133a01/Firefox.app/Contents/MacOS/firefox ; exit;
libc++abi.dylib: __cxa_guard_acquire detected deadlock
It never displays anything after this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
Can confirm the same behaviour on the real MBP 8,1 with 10.13.6.
|
i have verified the hang on the most recent versions.
the problem has to do with a change in mozjemalloc between 128 and 130
if you use 128.0, it will work fine.
i’ll try to find out what happened.
thanks for the information.
Thanks,
Gagan
… On Oct 24, 2024, at 1:24 AM, shakhbazian ***@***.***> wrote:
Can confirm the same behaviour on the real MBP 8,1 with 10.13.6.
Okay, fresh 10.13 Virtual Machine.
Firefox 133a01 was downloaded from Github via the preinstalled Safari 11.1.2.
I right click Firefox.app and select open to bypass Gatekeeper (this is a fresh VM, so Gatekeeper is enabled). I confirm that I want to run an app from an unidentified developer. Firefox behavior matches the video in the first post. Ditto when I force quit and open it again.
This was the part where I was hoping I could use the method I described in my last post to make Firefox work. Unfortunately, starting the binary directly doesn't seem to help in my VM. Terminal displays:
Last login: Wed Oct 23 21:03:41 on ttys000
/Users/jonathan/Downloads/133a01/Firefox.app/Contents/MacOS/firefox ; exit;
Jonathans-Mac:~ jonathan$ /Users/jonathan/Downloads/133a01/Firefox.app/Contents/MacOS/firefox ; exit;
libc++abi.dylib: __cxa_guard_acquire detected deadlock
It never displays anything after this.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
johnny @Wowfunhappy do you think you could help me out and see if this problem exists on a 10.12 and/or a 10.14 as well? i need to find out if the re-entrancy i’m witnessing is because of the 10.13 libc++ or something. i experienced this same issue on 10.14, for sure. but the weird thing is for all of us, once it’s working, it’s fine. this for sure has never happened on 10.8 or 10.9, probably not 10.10 or 10.11 either.
|
I'm sorry, at the moment I only have VMs for: 10.4 / Tiger I used to have everything between 10.4 – 10.13, but I had to clean some out because I just don't have the hard drive space. I might be able to spin up some 10.12 and/or 10.14 machines this weekend, I'm not sure. |
it’s all good.
has me thinking about what the issue could be. and others have reported it working fine, right?
at least it’s been narrowed down further. i can’t even get the text to print on command line when this issue arises.
it has to be something super early. i don’t even know if the mozjemalloc/phc stuff is relevant here, could be a red herring and be something in xre
at least we have something that’s reproducible.
… On Oct 24, 2024, at 5:06 PM, Jonathan ***@***.***> wrote:
I'm sorry, at the moment I only have VMs for:
10.4 / Tiger
10.6 / Snow Leopard
10.8 / Mountain Lion
10.9 / Mavericks
10.13 / High Sierra
I used to have everything between 10.4 – 10.13, but I had to clean some out because I just don't have the hard drive space.
I might be able to spin up some 10.12 and/or 10.14 machines this weekend, I'm not sure.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
I found the issue @Wowfunhappy. It has to do with the random number generation used for small memory allocations, which uses arc4random_buf. The comments in the Mozilla code suggested this can cause deadlocks. Removing arc4ranfom and using a pipe to dev/urandom fixed it, but I am talking to the Mozilla team to better understand the issue. It affects a fresh 10.12 too, and probably 10.14 (untested) as well. Haven't tried 10.15 but it wouldn't surprise me if it works fine since 10.15 uses unfair locks. I will test that too. |
confirmed that this is probably limited to 10.12<=osVersion<=10.14. 10.15 works fine: Screen.Recording.2024-10-26.at.11.35.59.AM.mp4so it has to do with the changes made to the allocator and their expectation that os_unfair_lock will be used with a flag that isn't available in 10.12->10.14. nor can we use osspinlock lol. i'll think of something. |
@Wowfunhappy try the latest build, it should be fixed. enjoy |
Yes, I can confirm this works in my 10.13 VM, starting from a fresh snapshot and using the exact same process as before! |
would you mind closing this if you feel the issue has been addressed @Wowfunhappy? i know it's not your ticket but i doubt the poster uses github that much. |
I would have already but I can't close other people's tickets. (I think you can as the repo owner, right?) |
oh that's right. "privileges" and whatnot. i hate doing tht though. but oh well. |
Keeps jumping in dock, then sits there 'not responding'
Attached is a 2min clip of it jumping and then sitting at not responding
Untitled.mov
The text was updated successfully, but these errors were encountered: