[AC-1001] [ERROR] Application Installer abnormal process termination. Process exit value was 8
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | n/a |
| Status | Closed |
| Resolution | Cannot Reproduce |
| Resolution Date | 2014-07-29T07:05:33.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | Titanium SDK & CLI |
| Labels | android |
| Reporter | Thanh Long |
| Assignee | Mauro Parra-Miranda |
| Created | 2014-06-30T02:47:35.000+0000 |
| Updated | 2016-03-08T07:37:19.000+0000 |
Hello, looks like a problem with your Android setup. The error number 8 is an error of memory (i.e., you don't have enough memory to run the emulator). Check your AVD manager and see how much memory is the emulator using. If possible, test your android project with an actual device. Best Regards,
Thank you for quick response. However, Emulator "titanium_1_WVGA800" was default setting with 512MiB while my computer is 8GiB RAM. I think it is OK! Secondly, while I connected device (Galaxy S), the device seemed not be recognized. Do you have any ideas about this? Thanks and best regards!
Hello! Some things to check when a device is not recognized: 1. Did you enable the developer feature in the device? http://developer.android.com/tools/device.html 2. Did you press ok in the "trust this machine" dialog? 3. Can you check if your usb cable is transmitting data as well? (Some USB Cables only provide power, but they don't have the wiring for the data). 4. Press "refresh devices" in the Ti Studio 5. Unlock your device when testing. 6. Install the USB drivers for your device (in the case of Samsung, you have to search for "Samsung Galaxy USB Developer drivers". Best Regards,
Thanks. I've done those steps above but... Actually, I used adb devices to check device. It appeared, but in Ti Studio list device is still empty. Unbelivable! What wrong with this? ========================================== C:\android-sdk-win\platform-tools>adb devices List of devices attached 0b9b9171 device ==========================================
I wondered what go wrong with longjohn.js as below. Now it appeared as a new bug. ========================================================================= C:\Users\n0267\AppData\Roaming\npm\node_modules\titanium\node_modules\longjohn\d ist\longjohn.js:185 throw e; ^ Error: EPERM, operation not permitted 'C:\Program Files\Windows NT\繧｢繧ｯ繧ｻ繧ｵ 繝ｪ' at fs.readdirSync (fs.js:654:18) at scan (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\titan ium-sdk\lib\emulators\genymotion.js:138:25) at scan (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\titan ium-sdk\lib\emulators\genymotion.js:150:26) at scan (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\titan ium-sdk\lib\emulators\genymotion.js:150:26) at C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\titanium-sd k\lib\emulators\genymotion.js:156:10 at C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\titanium-sd k\lib\emulators\genymotion.js:113:8 at q.process (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\ async\lib\async.js:731:21) at processImmediate (timers.js:336:15) --------------------------------------------- at async.setImmediate (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node _modules\async\lib\async.js:96:15) at C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\async\lib\a sync.js:696:21 at Array.forEach (native) at _each (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\asyn c\lib\async.js:32:24) at _insert (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\as ync\lib\async.js:681:11) at q.push (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\asy nc\lib\async.js:708:15) at C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\titanium-sd k\lib\emulators\genymotion.js:129:12 at queue.drain (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_module s\node-appc\lib\subprocess.js:108:3) --------------------------------------------- at async.setImmediate (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node _modules\async\lib\async.js:96:15) at C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\async\lib\a sync.js:696:21 at Array.forEach (native) at _each (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\asyn c\lib\async.js:32:24) at _insert (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\as ync\lib\async.js:681:11) at q.push (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_modules\asy nc\lib\async.js:708:15) at Object.findExecutable (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\n ode_modules\node-appc\lib\subprocess.js:113:8) at async.parallel.virtualbox (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3. GA\node_modules\titanium-sdk\lib\emulators\genymotion.js:99:20) --------------------------------------------- at Connection.exec (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3.GA\node_mo dules\titanium-sdk\lib\adb.js:213:9) at conn.exec.dontWaitForData (C:\ProgramData\Titanium\mobilesdk\win32\3.2.3. GA\node_modules\titanium-sdk\lib\adb.js:440:9) at Connection.
Hello! Looks like that issue only happens when you have your Antivirus software on (it will analyze the file before running it, therefore generates a race condition). Please shut down the antivirus software and then try again. Best Regards
Tried with a clean machine without antivirus. The issue didn't appear. Tested with 3.3.0.GA.