IINA 0.0.15.1 doesn't open in EL Capitan #1660
Comments
|
@saagarjha Yep, it's exactly the same crash, but I cannot figure out why. I'm using the usual way to compile the libraries. @blaqkr Could you try if 1.0.0-beta1 works? |
|
@lhc70000 the 1.0.0 beta works fine, I don't experience any problems |
|
@blaqkr Could you try if this build works? Thanks. https://drive.google.com/file/d/1jWopARzP_7KMLjvaenveJR4bu1h8LHzv/view?usp=sharing Two changes in this build:
(Otherwise, I can't find any difference between the |
|
@lhc70000 that has the same problem, it crashes on launch |
|
@blaqkr What computer are you using? Is it something that's relatively old? |
|
@lhc70000 How are you building these? What hardware are you using? |
|
A MacBook Early 2013 with latest macOS, a modified Homebrew to inject |
|
Can you give me an exact processor version? |
|
@saagarjha i7-3740QM. |
|
I'm waiting for @blaqkr to chime in, but I strongly suspect that this is because the version of libglib-2.0.0 that you compiled for 0.0.15.1 uses Intel AVX instructions, which most modern Macs support, but @blaqkr's computer doesn't. For example, I disassembled libglib-2.0.0 and there's a What is the exact compile command you used to compile libglib-2.0.0? |
|
@saagarjha Thanks, that makes lots of sense. All I do is like running I'm curious about:
|
|
(seems that at least I can override this in homebrew without touching compiler flags.) |
|
I think the general way this is handled is by creating a fat binary with both "architectures" glommed together. |
|
@saagarjha Thanks. I think it's time to set up our own build system (it can be like just a shell script). There're too much obscured configurations hiding in homebrew. I'm not sure if I have enough time to do this recently, so It would be great if anyone could help. Probably we need a brew formula too. |
|
Yeah, I was thinking it's probably time to set up some sort of build system for IINA. Unfortunately, I'm extremely busy this week so I can't spend much time on it, but I'm free to work on this over the weekend. |
|
@saagarjha MacBook Pro late 2007, processor says Intel Core 2 Duo |
|
Yeah, that seems to confirm my theory that your processor just doesn't support AVX at all, so it's crashing because it's attempting to perform what its view is an invalid instruction. Your issue seems to be one that affected many people a while back, so it's great to see a cause for this bug be identified! Edit: By the way, props to you for keeping an eleven-year-old computer up and running! |
|
I just realized that, maybe homebrew won't propagate the I'll try to build all libs separately with |
|
@blaqkr Could you try this build again? https://drive.google.com/file/d/1VA5LiySx2SNxC8_gApkhfBhld9Gyy9se/view?usp=sharing |
|
@lhc70000 problem solved, seems to be working fine: opens, plays local files, takes screenshots, streams from YouTube... |
|
Just my two cents, if you want to have stable and reproducible build, you probably want:
Side note: There will be some performance penalty if you disable AVX on supported machine, which is used for SIMD and is a part of hardware acceleration. |
|
Neither 0.0.13 (44), 0.0.14.1 (55), 0.0.15.1 (69) or 1.0.0-beta2 (80) will start on my El Capitan MacBook Pro (10.11.6). IINA_2018-07-05-155732_rMBP.hang.log |
System and IINA version:
Expected behavior:
Start app and show welcome screen
Actual behavior:
icon bounces on the dock a couple of times then stops, the app can't be opened even after a clean install
Steps to reproduce:
open app from Finder
How often does this happen?
all the time
The text was updated successfully, but these errors were encountered: