- A mac computer simultaneously run multiple iOS appium Service
- Used to always start in a mac computer iOS appium a service in another computer mac start a virtual machine iOS appium service, found on a virtual machine running an automated script for a long time will be very slow to see Appium Discuss forum finally found a solution
- iOS Appiam a 服务, 4723 --tmp appium -p / tmp / tmp4723
- iOS appium B 服务, 4724 --tmp appium -p / tmp / tmp4724
- Note: tmp parameters essential, otherwise the problem when running server script constantly switch to switch less than another server will appear
- Used to always start in a mac computer iOS appium a service in another computer mac start a virtual machine iOS appium service, found on a virtual machine running an automated script for a long time will be very slow to see Appium Discuss forum finally found a solution
- Android appium server performs automated scripts over one hour always reported FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory out of memory
- By adjusting \ \ appium.cmd in --max-old-space-size memory size limit parameter value node_modules.bin \ Appium
@IF EXIST "%~dp0\node.exe" ( "%~dp0\node.exe" "%~dp0\..\appium\bin\appium.js" %* ) ELSE ( node --max-old-space-size=2047 --gc-global "%~dp0\..\appium\bin\appium.js" %* )
Note: - max-old-space- size parameter value more than 2047, such as the server 2048 to start appium also reported FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory to view the relevant information, the original Node V8 doing a memory limit, limiting the JavaScript memory that can be used (64 to 1.9GB, 32-bit 1GB), temporarily it do not understand why this restriction.
- By adjusting \ \ appium.cmd in --max-old-space-size memory size limit parameter value node_modules.bin \ Appium
Appium summary appium problem for some time solutions (turn)
Guess you like
Origin www.cnblogs.com/zhangziyu-2018/p/9316049.html
Ranking