Genymotion incidente su start in OSX

Question

io sono l'uso di Mac OS El Capitan 10.11.5

installata VirtualBox 5.0.24

Genymotion 2.7.2

E quando sto iniziando Genymotion ottengo incidente - vedi immagine: -

testo dalla relazione crash

Process:    genymotion [1051] 
Path:     /Applications/Genymotion.app/Contents/MacOS/genymotion 
Identifier:   com.yourcompany.genymotion 
Version:    ??? 
Code Type:    X86-64 (Native) 
Parent Process:  ??? [1] 
Responsible:   genymotion [1051] 
User ID:    501 

Date/Time:    2016-07-03 10:38:17.680 +0300 
OS Version:   Mac OS X 10.11.5 (15F34) 
Report Version:  11 
Anonymous UUID:  890BAC95-7988-7846-0ECE-0DEC8BFB2C9E 

Sleep/Wake UUID:  10886C01-28E6-49CC-B63D-2AA32EEC3A87 

Time Awake Since Boot: 6500 seconds 
Time Since Wake:  3700 seconds 

System Integrity Protection: enabled 

Crashed Thread:  0 Dispatch queue: com.apple.main-thread 

Exception Type:  EXC_BAD_INSTRUCTION (SIGILL) 
Exception Codes:  0x0000000000000001, 0x0000000000000000 
Exception Note:  EXC_CORPSE_NOTIFY 

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 
0 libcrypto.1.0.0.dylib   0x0000000103f1e758 lh_new + 196 
1 libcrypto.1.0.0.dylib   0x0000000103e70467 OBJ_NAME_init + 48 
2 libcrypto.1.0.0.dylib   0x0000000103e70780 OBJ_NAME_add + 34 
3 libcrypto.1.0.0.dylib   0x0000000103f27f3f EVP_add_cipher + 42 
4 libcrypto.1.0.0.dylib   0x0000000103f2b9cd OpenSSL_add_all_ciphers + 19 
5 libcrypto.1.0.0.dylib   0x0000000103f2b9b4 OPENSSL_add_all_algorithms_noconf + 14 
6 com.yourcompany.genymotion  0x0000000103cde27c 0x103bf6000 + 950908 
7 com.yourcompany.genymotion  0x0000000103c9011a 0x103bf6000 + 631066 
8 com.yourcompany.genymotion  0x0000000103c975bb 0x103bf6000 + 660923 
9 com.yourcompany.genymotion  0x0000000103c871d5 0x103bf6000 + 594389 
10 com.yourcompany.genymotion  0x0000000103ca47f6 0x103bf6000 + 714742 
11 com.yourcompany.genymotion  0x0000000103c04277 0x103bf6000 + 57975 
12 com.yourcompany.genymotion  0x0000000103bfc324 0x103bf6000 + 25380 
13 com.yourcompany.genymotion  0x0000000103bfbf84 0x103bf6000 + 24452 

Thread 1:: Dispatch queue: com.apple.libdispatch-manager 
0 libsystem_kernel.dylib   0x00007fff8865befa kevent_qos + 10 
1 libdispatch.dylib    0x00007fff90cfe165 _dispatch_mgr_invoke + 216 
2 libdispatch.dylib    0x00007fff90cfddcd _dispatch_mgr_thread + 52 

Thread 2: 
0 libsystem_kernel.dylib   0x00007fff8865b5e2 __workq_kernreturn + 10 
1 libsystem_pthread.dylib   0x00007fff981c1578 _pthread_wqthread + 1283 
2 libsystem_pthread.dylib   0x00007fff981bf341 start_wqthread + 13 

Thread 3: 
0 libsystem_kernel.dylib   0x00007fff8865b5e2 __workq_kernreturn + 10 
1 libsystem_pthread.dylib   0x00007fff981c1578 _pthread_wqthread + 1283 
2 libsystem_pthread.dylib   0x00007fff981bf341 start_wqthread + 13 

Thread 4: 
0 libsystem_kernel.dylib   0x00007fff8865b5e2 __workq_kernreturn + 10 
1 libsystem_pthread.dylib   0x00007fff981c1578 _pthread_wqthread + 1283 
2 libsystem_pthread.dylib   0x00007fff981bf341 start_wqthread + 13 

Thread 5: 
0 libsystem_kernel.dylib   0x00007fff8865b5e2 __workq_kernreturn + 10 
1 libsystem_pthread.dylib   0x00007fff981c1578 _pthread_wqthread + 1283 
2 libsystem_pthread.dylib   0x00007fff981bf341 start_wqthread + 13 

Thread 6: 
0 libsystem_kernel.dylib   0x00007fff8865b5e2 __workq_kernreturn + 10 
1 libsystem_pthread.dylib   0x00007fff981c1578 _pthread_wqthread + 1283 
2 libsystem_pthread.dylib   0x00007fff981bf341 start_wqthread + 13 

Thread 7: 
0 libsystem_kernel.dylib   0x00007fff8865b5e2 __workq_kernreturn + 10 
1 libsystem_pthread.dylib   0x00007fff981c1578 _pthread_wqthread + 1283 
2 libsystem_pthread.dylib   0x00007fff981bf341 start_wqthread + 13 

Thread 8: 

Thread 9:: Qt bearer thread 
0 libsystem_kernel.dylib   0x00007fff8865ad3e __pselect + 10 
1 libsystem_kernel.dylib   0x00007fff88658274 pselect$1050 + 82 
2 org.qt-project.QtCore   0x0000000104f09cc8 qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) + 104 
3 org.qt-project.QtCore   0x0000000104f0ad80 QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timespec*) + 672 
4 org.qt-project.QtCore   0x0000000104f0be4a QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 234 
5 org.qt-project.QtCore   0x0000000104eb637d QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 381 
6 org.qt-project.QtCore   0x0000000104cac4d5 QThread::exec() + 117 
7 org.qt-project.QtCore   0x0000000104caff63 0x104c7b000 + 216931 
8 libsystem_pthread.dylib   0x00007fff981c199d _pthread_body + 131 
9 libsystem_pthread.dylib   0x00007fff981c191a _pthread_start + 168 
10 libsystem_pthread.dylib   0x00007fff981bf351 thread_start + 13 

Thread 0 crashed with X86 Thread State (64-bit): 
    rax: 0x0000000103e70488 rbx: 0x00007f91c951f880 rcx: 0x000000000000000f rdx: 0x0000000000000000 
    rdi: 0x0000000107b58a00 rsi: 0x00007f91c9500000 rbp: 0x00007fff5c009340 rsp: 0x00007fff5c009320 
    r8: 0x0000000000000007 r9: 0x00000000fffffe00 r10: 0x0000000000000012 r11: 0x00007f91c9500000 
    r12: 0x0000000103f88cf2 r13: 0x0000000000000000 r14: 0x0000000103e70488 r15: 0x0000000103e704d5 
    rip: 0x0000000103f1e758 rfl: 0x0000000000010206 cr2: 0x00000001050518a0 

Logical CPU:  0 
Error Code:  0x0200018a 
Trap Number:  133 

se inizio dal terminal ricevo testo accanto

iMac-Alex-Neo:~ alexneo$ /Applications/Genymotion.app/Contents/MacOS/genymotion ; exit; 
Logging activities to file: /Users/alexneo/.Genymobile/genymotion.log 
Illegal instruction: 4 
logout 
Saving session... 
...copying shared history... 
...saving history...truncating history files... 
...completed. 
Deleting expired sessions...none found. 

[Process completed] 

Answer 1

appena capito come forzare Genymotion 2.7.2 a lavorare su OS X.

Si dovrebbe avere Genymotion 2.7.2 e homebrew installato.

brew install openssl 

o se lo avete già installato

brew upgrade openssl 
brew cleanup 

ricordare: trovare restituisce una lista (vecchi pacchetti homebrew saranno inclusi), quindi se avete diverse versioni di OpenSSL homebrew si dovrebbe saltare terzo comando (cp find stadio) e copia openssl dylib manualmente

Fix per: Genymotion.app

cd /Applications/Genymotion.app/Contents/Frameworks 
mv libcrypto.1.0.0.dylib libcrypto.1.0.0.dylib.bak 
sudo cp `find /usr/local/Cellar/openssl -name libcrypto.1.0.0.dylib` /Applications/Genymotion.app/Contents/Frameworks/ 

Correzione per: Shell di genio.App

cd /Applications/Genymotion\ Shell.app/Contents/Frameworks 
mv libcrypto.1.0.0.dylib libcrypto.1.0.0.dylib.bak 
sudo cp `find /usr/local/Cellar/openssl -name libcrypto.1.0.0.dylib` /Applications/Genymotion\ Shell.app/Contents/Frameworks/ 

P.S.: sembra che libcrypto.1.0.0.dylib in Genymotion 2.7.0 - 2.7.2 è stato costruito per Sandy Bridge o le nuove CPU e schiantarsi su istruzione vxorps% xmm0,% xmm0,% xmm0

EDIT: perse comandi per aggiornare player.app incorporato (genymotion strumento VM), ma abbiamo bisogno di aggiornare troppo ... se vogliamo eseguire VM ;-)

Fix per: player.app

cd /Applications/Genymotion.app/Contents/MacOS/player.app/Contents/Frameworks 
mv libcrypto.1.0.0.dylib libcrypto.1.0.0.dylib.bak 
sudo cp `find /usr/local/Cellar/openssl -name libcrypto.1.0.0.dylib` /Applications/Genymotion.app/Contents/MacOS/player.app/Contents/Frameworks/ 

Ora Genymotion 2.7.2 lavora

Answer 2

Upd. Eseguo il downgrade alla versione 2.6.0 e risolvo questo problema.

Answer 3

Posso confermare che Genymotion 2.6.0 funziona su un Mac che presenta questo problema. Scarica link

Answer 4

posso confermare questo con OS 10.11.5, Genymotion 2.7.0 o 2.7.1 o la 2.7.2 reale utilizzando l'attuale VirtualBox 5.0.24

ho anche uninstalled Genymotion totally come detto nelle FAQ, fare questo:

rm $HOME/.Genymobile/genymotion* 
rm -rf $HOME/.Genymobile/Genymotion 
rm -rf "~/Library/Preferences/com.genymobile.genymotion.plist" "~/Library/Saved Application State/com.genymobile.genymotion.savedState" 
killall -u $USER cfprefsd 

Ma nessun cambiamento. Tutte e tre le versioni 2.7.0, 2.7.1 e 2.7.2 non funzionano, perché si bloccano immediatamente all'avvio, anche con una precedente disinstallazione pulita.

Genymotion 2.6.0 funziona, come gli altri hanno scritto. Ma ora ci sono delle differenze tra le immagini, nel download ottengo le immagini 2.7.2 e non più le immagini 2.6.0, che danno anche avvertimenti e difficoltà.

Ho chiesto il supporto e posterò qui i risultati se ci sono.

Frank