question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Appium/Nodejs goes out of memory after a long time running

See original GitHub issue

Hi,

We’re trying to run a lot of test scripts in a row against Android on Windows7. And in the middle of test run Nodejs says that process out of memory and test run breaks up.

I’m using:

  • Nodejs v0.10.26
  • Appium v0.18.0 (the latest v1.0.0 did not tested yet - need to update Xpath locators)

Here’s more detailed appium log:

execute HTTP/1.1" 200 89 "-" "-"
info: [BOOTSTRAP] [info] Swiping from [x=648.0, y=592.0] to [x=72.0, y=592.0] wi
th steps: 28
info: [BOOTSTRAP] [info] Returning result: {"value":true,"status":0}
debug: Appium request initiated at /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574
edaa558/elements
debug: Request received with params: {"using":"id","value":"com.lgi.orionandroid
:id/date_picker_button"}
info: Pushing command to appium work queue: ["find",{"strategy":"id","selector":
"com.lgi.orionandroid:id/date_picker_button","context":"","multiple":true}]
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"find","
params":{"strategy":"id","selector":"com.lgi.orionandroid:id/date_picker_button"
,"context":"","multiple":true}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: find
info: [BOOTSTRAP] [debug] Finding com.lgi.orionandroid:id/date_picker_button usi
ng ID with the contextId:
info: [BOOTSTRAP] [info] Element[] is null: (0)
info: [BOOTSTRAP] [info] Element[] is null: (1)
info: [BOOTSTRAP] [info] Returning result: {"value":[{"ELEMENT":"75"}],"status":
0}
info: Responding to client with success: {"status":0,"value":[{"ELEMENT":"75"}],
"sessionId":"7b723ca2-8b35-473e-95bb-1d574edaa558"}
POST /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/elements 200 709ms - 1
24b
debug: 127.0.0.1 - - "POST /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/
elements HTTP/1.1" 200 124 "-" "-"
debug: Appium request initiated at /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574
edaa558/elements
debug: Request received with params: {"using":"id","value":"com.lgi.orionandroid
:id/dateFilter"}
info: Pushing command to appium work queue: ["find",{"strategy":"id","selector":
"com.lgi.orionandroid:id/dateFilter","context":"","multiple":true}]
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"find","
params":{"strategy":"id","selector":"com.lgi.orionandroid:id/dateFilter","contex
t":"","multiple":true}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: find
info: [BOOTSTRAP] [debug] Finding com.lgi.orionandroid:id/dateFilter using ID wi
th the contextId:
info: [BOOTSTRAP] [info] Returning result: {"value":[],"status":0}
info: Responding to client with success: {"status":0,"value":[],"sessionId":"7b7
23ca2-8b35-473e-95bb-1d574edaa558"}
POST /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/elements 200 693ms - 8
7b
debug: 127.0.0.1 - - "POST /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/
elements HTTP/1.1" 200 87 "-" "-"
debug: Appium request initiated at /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574
edaa558/element/75/attribute/text
debug: Request received with params: {}
info: Pushing command to appium work queue: ["element:getAttribute",{"elementId"
:"75","attribute":"text"}]
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"element
:getAttribute","params":{"elementId":"75","attribute":"text"}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: getAttribute
info: [BOOTSTRAP] [info] Returning result: {"value":"TODAY","status":0}
info: Responding to client with success: {"status":0,"value":"TODAY","sessionId"
:"7b723ca2-8b35-473e-95bb-1d574edaa558"}
GET /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/element/75/attribute/te
xt 200 1154ms - 92b
debug: 127.0.0.1 - - "GET /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/e
lement/75/attribute/text HTTP/1.1" 200 92 "-" "-"
debug: Appium request initiated at /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574
edaa558/elements
debug: Request received with params: {"using":"id","value":"com.lgi.orionandroid
:id/date_picker_button"}
info: Pushing command to appium work queue: ["find",{"strategy":"id","selector":
"com.lgi.orionandroid:id/date_picker_button","context":"","multiple":true}]
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"find","
params":{"strategy":"id","selector":"com.lgi.orionandroid:id/date_picker_button"
,"context":"","multiple":true}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: find
info: [BOOTSTRAP] [debug] Finding com.lgi.orionandroid:id/date_picker_button usi
ng ID with the contextId:
info: [BOOTSTRAP] [info] Element[] is null: (0)
info: [BOOTSTRAP] [info] Element[] is null: (1)
info: [BOOTSTRAP] [info] Returning result: {"value":[{"ELEMENT":"76"}],"status":
0}
info: Responding to client with success: {"status":0,"value":[{"ELEMENT":"76"}],
"sessionId":"7b723ca2-8b35-473e-95bb-1d574edaa558"}
POST /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/elements 200 1347ms -
124b
debug: 127.0.0.1 - - "POST /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/
elements HTTP/1.1" 200 124 "-" "-"
debug: Appium request initiated at /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574
edaa558/elements
debug: Request received with params: {"using":"id","value":"com.lgi.orionandroid
:id/dateFilter"}
info: Pushing command to appium work queue: ["find",{"strategy":"id","selector":
"com.lgi.orionandroid:id/dateFilter","context":"","multiple":true}]
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"find","
params":{"strategy":"id","selector":"com.lgi.orionandroid:id/dateFilter","contex
t":"","multiple":true}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: find
info: [BOOTSTRAP] [debug] Finding com.lgi.orionandroid:id/dateFilter using ID wi
th the contextId:
info: Responding to client with success: {"status":0,"value":[],"sessionId":"7b7
23ca2-8b35-473e-95bb-1d574edaa558"}
POST /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/elements 200 57ms - 87
b
debug: 127.0.0.1 - - "POST /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/
elements HTTP/1.1" 200 87 "-" "-"
info: [BOOTSTRAP] [info] Returning result: {"value":[],"status":0}
debug: Appium request initiated at /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574
edaa558/element/76/attribute/text
debug: Request received with params: {}
info: Pushing command to appium work queue: ["element:getAttribute",{"elementId"
:"76","attribute":"text"}]
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"element
:getAttribute","params":{"elementId":"76","attribute":"text"}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: getAttribute
info: [BOOTSTRAP] [info] Returning result: {"value":"TODAY","status":0}
info: Responding to client with success: {"status":0,"value":"TODAY","sessionId"
:"7b723ca2-8b35-473e-95bb-1d574edaa558"}
GET /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/element/76/attribute/te
xt 200 1350ms - 92b
debug: 127.0.0.1 - - "GET /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/e
lement/76/attribute/text HTTP/1.1" 200 92 "-" "-"
debug: Appium request initiated at /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574
edaa558/screenshot
debug: Request received with params: {}
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 shell "/system/bin/rm /data/local/tmp/screenshot.png; /system/bin/scree
ncap -p /data/local/tmp/screenshot.png "
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 pull /data/local/tmp/screenshot.png "C:\\Users\\SIARHE~1.MIN\\AppData\\
Local\\Temp\\appium11447-8484-mhwvr0.png"
info: Responding to client with success: {"status":0,"value":"iVBORw0KGgoAAAANSU
hEUgAAAtAAAAUACAYAAABuzmU9AAAABHNCSVQICAgIfAhkiAAAIABJREFUeJzsvXecVdW5///Zp01lKj
CUofcBpErRKAoWxE5iiyaaxEtyvfcmmmLU5Bo1McV8o0ksye/G+FKjRpGIiiBFMIB06QpDlz4zMEyvp+
zfH7iP+6xZbe9TZkae9+sF5+y1nvWsZ+29z9mf/cw6axsATBAEQRAEQRAEoYWnvQMgCIIgCIIgiM4ECW
iCIAiCIAiCcAAJaIIgCIIgCIJwAAlogiAIgiAIgnAACWiCIAiCIAiCcAAJaIIgCIIgCIJwAAlogiAIgi
A6JIZhRP91FjpTrIR7DNA60ARBEARBtDOW8DQMA5FIRGjn8Xhgmmeli/Xa0bBijDc+b1o6vGkZQj+GYS
Dc0oRwS3Nc/RDO8bV3AARBEARBnFvYs7SsGLZevV4vfL4vZEooFEI4HOaKa56/VGO/ARg/fjy2b9+OYD
DowMEXkwIMrweIRNB7+mz0uerriARb22S2TdOExx/A0fdfw9ElrwMeD8ywbd+Y4psQIn5IQBMEQRAEkR
IsEWgXuT6fD9nZ2ejRowfy8vKQmZmJnJwcpKenIz09PWrX3NyM5uZm1NbWorGxEdXV1SgrK0N9fT1CoZ
C0j1RhmibGjRuHPn36YMuWLQ4bfyF4zdDZ94bPD19GFpCRJWxm+PwwIxFAkrUnEg8JaIIgCIIgkophGD
FTGrKzs9G7d28UFxdjwIABKCgoiIplj0f98ywrC93c3IwzZ87g0KFDOHbsGI4fP476+vo2/SYbq5/hw4
djyJAhaGpqcjQX2vB4kNO9FzxeH0zThOHxINjagoycPODz/cbLQBuGgYycPGR37wV/IA1mJHJ2Ckw4hN
qKE2eFNZEUaA40QRAEQRBJgRWwvXv3RklJCYYMGYKuXbvCMAzXc5rZOdOmaeL06dPYt28fdu3ahePHjw
vjSCQejweRSAT9+vXDpEmT...","sessionId":"7b723ca2-8b35-473e-95bb-1d574edaa558"}
GET /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/screenshot 200 112444ms
 - 226.56kb
debug: 127.0.0.1 - - "GET /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558/s
creenshot HTTP/1.1" 200 231995 "-" "-"
debug: Appium request initiated at /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574
edaa558
debug: Request received with params: {}
info: Shutting down appium session...
info: [ADB] Pressing the HOME button
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 shell "input keyevent 3"
info: Stopping logcat capture
debug: Logcat terminated with code null, signal SIGTERM
info: Sent shutdown command, waiting for UiAutomator to stop...
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"shutdown"}
info: [BOOTSTRAP] [info] Got command of type SHUTDOWN
info: [BOOTSTRAP] [info] Returning result: {"value":"OK, shutting down","status"
:0}
info: [BOOTSTRAP] [info] Closed client connection
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.boots
trap.Bootstrap
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
info: [UIAUTOMATOR STDOUT] Time: 1207.728
info: [UIAUTOMATOR STDOUT] OK (1 test)
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
warn: UiAutomator did not shut down fast enough, calling it gone
info: Cleaning up android objects
info: Cleaning up appium session
info: Responding to client with success: {"status":0,"value":null,"sessionId":"7
b723ca2-8b35-473e-95bb-1d574edaa558"}
DELETE /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa558 200 10937ms - 89b
debug: 127.0.0.1 - - "DELETE /wd/hub/session/7b723ca2-8b35-473e-95bb-1d574edaa55
8 HTTP/1.1" 200 89 "-" "-"
debug: Appium request initiated at /wd/hub/session
debug: Request received with params: {"desiredCapabilities":{"newCommandTimeout"
:"120","app":"D:\\\\orion_android.apk","host-machine":{"username":null,"hostname
":"127.0.0.1","password
":null,"hCode":-139673956},"device-ready-timeout":"120","app-package":"com.lgi.o
rionandroid","launchTimeout":"120000","proxy-port":null,"device":"android","app-
activity":".ui.activity.SignInActivity","version":"4.3"}}
warn: Converting cap host-machine to string, since it was an object. This might
be a user error. Original value was: {"username":null,"hostname":"127.0.0.1",
"password":null,"hCode":-139673956}
info: Using local app from desired caps: D:\orion_android.apk
info: Creating new appium session 6a076242-e26b-4466-88c9-6c6390db1142
info: Starting android appium
debug: Using fast reset? true
info: Preparing device for session
info: Checking whether app is actually present
info: Checking whether adb is present
info: [ADB] Using adb from d:\android-sdk-windows\platform-tools\adb.exe
info: Trying to find a connected android device
info: [ADB] Getting connected devices...
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" devices
info: [ADB] 1 device(s) connected
info: Setting device id to 192.168.56.101:5555
info: [ADB] Waiting for device to be ready and to respond to shell commands (tim
eout = 120)
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 wait-for-device
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 shell "echo 'ready'"
info: Starting logcat capture
info: Getting device API level
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 shell "getprop ro.build.version.sdk"
info: Device is at API Level 18
debug: java -jar "D:\Mobile_CRS\APPIUM\Appium_v0.18.0\node_modules\appium\lib\de
vices\android\helpers\strings_from_apk.jar" "D:\orion_android.apk" "C:\Windows\T
emp\com.lgi.orionandroid"
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 push "C:\\Windows\\Temp\\com.lgi.orionandroid\\strings.json" /data/loca
l/tmp
info: Checking whether aapt is present
info: [ADB] Using aapt from d:\android-sdk-windows\build-tools\19.0.1\aapt.exe
debug: processFromManifest: "d:\android-sdk-windows\build-tools\19.0.1\aapt.exe"
 dump xmltree D:\orion_android.apk AndroidManifest.xml
debug: Set app process to: gi.orionandroid
debug: Not uninstalling app since server not started with --full-reset
debug: Checking app cert for D:\orion_android.apk: java -jar "D:\Mobile_CRS\APPI
UM\Appium_v0.18.0\node_modules\appium\lib\devices\android\helpers\verify.jar" "D
:\orion_android.apk"
debug: App already signed.
info: Zip-aligning D:\orion_android.apk
info: Checking whether zipalign is present
info: [ADB] Using zipalign from d:\android-sdk-windows\tools\zipalign.exe
debug: zipAlignApk: "d:\android-sdk-windows\tools\zipalign.exe" -f 4 "D:\orion_a
ndroid.apk" "C:\Users\SIARHE~1.MIN\AppData\Local\Temp\appium11447-8484-1k7bhx4.t
mp"
info: MD5 for app is ca0a4d5bb3b03b7cd00212492fa5ba14
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 shell "ls /data/local/tmp/ca0a4d5bb3b03b7cd00212492fa5ba14.apk"
debug: Getting install status for com.lgi.orionandroid
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 shell "pm list packages -3 com.lgi.orionandroid"
info: [ADB] App is installed
info: Running fast reset (stop and clear)
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 shell "am force-stop com.lgi.orionandroid"
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 shell "pm clear com.lgi.orionandroid"
info: [ADB] Forwarding system:4724 to device:4724
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 forward tcp:4724 tcp:4724
debug: Pushing appium bootstrap to device...
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 push "D:\\Mobile_CRS\\APPIUM\\Appium_v0.18.0\\node_modules\\appium\\bui
ld\\android_bootstrap\\AppiumBootstrap.jar" /data/local/tmp/
debug: Pushing unlock helper app to device...
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 install "D:\Mobile_CRS\APPIUM\Appium_v0.18.0\node_modules\appium\build\
unlock_apk\unlock_apk-debug.apk"
info: Attempting to kill all 'uiautomator' processes
info: Getting all processes with 'uiautomator'
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 shell "ps 'uiautomator'"
info: No matching processes found
info: Running bootstrap
debug: spawning: d:\android-sdk-windows\platform-tools\adb.exe -s 192.168.56.101
:5555 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstr
ap.Bootstrap
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.boots
trap.Bootstrap
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
info: [BOOTSTRAP] [info] Socket opened on port 4724
info: [BOOTSTRAP] [info] Appium Socket Server Ready
info: [BOOTSTRAP] [info] Loading json...
info: [BOOTSTRAP] [info] json loading complete.
info: [BOOTSTRAP] [info] Registered crash watchers.
debug: Waking up device if it's not alive
info: Pushing command to appium work queue: ["wake",{}]
info: [BOOTSTRAP] [info] Client connected
info: [BOOTSTRAP] [info] Got data from client: {"cmd":"action","action":"wake","
params":{}}
info: [BOOTSTRAP] [info] Got command of type ACTION
info: [BOOTSTRAP] [debug] Got command action: wake
info: [BOOTSTRAP] [info] Returning result: {"value":true,"status":0}
debug: executing: "d:\android-sdk-windows\platform-tools\adb.exe" -s 192.168.56.
101:5555 shell "dumpsys window"
FATAL ERROR: CALL_AND_RETRY_2 Allocation failed - process out of memory

Is there any cure on this ?

Issue Analytics

  • State:closed
  • Created 9 years ago
  • Comments:15 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
cosminstirbucommented, Mar 30, 2017

Hello,

I have a similar issue with Appium 1.6.4-beta. We run our iOS tests nightly for almost 7 hours and at some point (during the last 1-2 hours) we kick off a new Appium instance on a different port to run the Android tests, and they overlap for almost 1 - 2 hours.

The issue is that the iOS tests crash some time after the Android tests start with the following stack trace:

[debug] [MJSONWP] Calling AppiumDriver.timeouts() with args: ["implicit",1000,"01227913-2361-48fb-a16b-98cbaa73266b"]
[debug] [XCUITest] Executing command 'timeouts'

<--- Last few GCs --->

[59843:0x102804600] 21441585 ms: Scavenge 1375.0 (1426FATAL ERROR: Scavenger: promoting marked
 Allocation failed - process out of memory
 1: .9) -> 1374.3 (1426.9) MB, 8.0 / 0.0 ms  (+ 1.8 ms in 509 steps since last GC) allocation failure 
[59843:0x102804600] 21441763 ms: Scavenge 1375.2 (1426.9) -> 1374.5 (1426.9) MB, 8.9 / 0.0 ms  (+ 1.0 ms in 523 steps since last GC) allocation failure 
[59843:0x102804600] 21441924 ms: Scavenge 1375.4 (1426.9) -> 1374.9 (1426.9) MB, 8.2 / 0.0 ms  (+ 1.9 ms in 536 steps since last GC) allocation failure 


<--- JS stacktrace --->
Cannot get stack trace in GC.
node::Abort() [/usr/local/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/bin/node]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
 4: v8::internal::FatalProcessOutOfMemory(char const*) [/usr/local/bin/node]
 5: void v8::internal::ScavengingVisitor<(v8::internal::MarksHandling)0, (v8::internal::PromotionMode)0, (v8::internal::LoggingAndProfiling)1>::EvacuateObject<(v8::internal::ScavengingVisitor<(v8::internal::MarksHandling)0, (v8::internal::PromotionMode)0, (v8::internal::LoggingAndProfiling)1>::ObjectContents)0, (v8::internal::AllocationAlignment)0>(v8::internal::Map*, v8::internal::HeapObject**, v8::internal::HeapObject*, int) [/usr/local/bin/node]
 6: v8::internal::Heap::IteratePromotedObjectPointers(v8::internal::HeapObject*, unsigned char*, unsigned char*, bool, void (*)(v8::internal::HeapObject**, v8::internal::HeapObject*)) [/usr/local/bin/node]
 7: void v8::internal::CallIterateBody::apply<v8::internal::FixedBodyDescriptor<24, 40, 40>, v8::internal::ObjectVisitor>(v8::internal::HeapObject*, int, v8::internal::ObjectVisitor*) [/usr/local/bin/node]
 8: v8::internal::Heap::IteratePromotedObject(v8::internal::HeapObject*, int, bool, void (*)(v8::internal::HeapObject**, v8::internal::HeapObject*)) [/usr/local/bin/node]
 9: v8::internal::Heap::DoScavenge(v8::internal::ObjectVisitor*, unsigned char*, v8::internal::PromotionMode) [/usr/local/bin/node]
10: v8::internal::Heap::Scavenge() [/usr/local/bin/node]
11: v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/local/bin/node]
12: v8::internal::Heap::CollectGarbage(v8::internal::GarbageCollector, char const*, char const*, v8::GCCallbackFlags) [/usr/local/bin/node]
13: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
14: v8::internal::OrderedHashTable<v8::internal::OrderedHashSet, v8::internal::JSSetIterator, 1>::Allocate(v8::internal::Isolate*, int, v8::internal::PretenureFlag) [/usr/local/bin/node]
15: v8::internal::KeyAccumulator::CollectOwnPropertyNames(v8::internal::Handle<v8::internal::JSReceiver>, v8::internal::Handle<v8::internal::JSObject>) [/usr/local/bin/node]
16: v8::internal::KeyAccumulator::CollectOwnKeys(v8::internal::Handle<v8::internal::JSReceiver>, v8::internal::Handle<v8::internal::JSObject>) [/usr/local/bin/node]
17: v8::internal::KeyAccumulator::CollectKeys(v8::internal::Handle<v8::internal::JSReceiver>, v8::internal::Handle<v8::internal::JSReceiver>) [/usr/local/bin/node]
18: v8::internal::FastKeyAccumulator::GetKeys(v8::internal::GetKeysConversion) [/usr/local/bin/node]
19: v8::internal::KeyAccumulator::GetKeys(v8::internal::Handle<v8::internal::JSReceiver>, v8::internal::KeyCollectionMode, v8::internal::PropertyFilter, v8::internal::GetKeysConversion, bool) [/usr/local/bin/node]
20: v8::internal::(anonymous namespace)::GetOwnPropertyKeys(v8::internal::Isolate*, v8::internal::BuiltinArguments, v8::internal::PropertyFilter) [/usr/local/bin/node]
21: 0x17d320c06167
22: 0x17d321e75c11
23: 0x17d321e750e8
24: 0x17d323812d24
25: 0x17d320c07e55

If I run a subset of them locally, they run in parallel without any issues.

The interesting part is that on the Continuous Integration server, even though the iOS ones crash, the Android ones keep running just fine.

Any ideas how I could fix this? Thank you!

0reactions
lock[bot]commented, Apr 29, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Appium / NodeJS - Memory Allocation Crash - Issues/Bugs
The issue is that the iOS tests crash some time after the Android tests start with the following stack trace:
Read more >
Appium forces JavaScript heap out of memory - Stack Overflow
That is definitely an issue: I cannot speak for older server version, but with 1.7.1 single node for me uses 115-180 Mb RAM...
Read more >
Top 50 Appium Interview Questions You Must Prepare In 2023
This article on Appium Interview Questions will help you ace your interviews and set you on the path of becoming a Appium Professional....
Read more >
Appium Interview Questions & Answers
Question: What About Performance impact while running tests using Appium? Answer : Appium is not a huge application and requires very little memory....
Read more >
Top 50 Selendroid interview questions and answers
3) List out the pre-requisite to use APPIUM? ... Running scripts on multiple iOS simulators at the same time is possible with Appium...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found