Single process mode creates a zygote process

While launching twitter I saw two zygote process running, it may related to same issue where extra zygote process is created

phablet@ubuntu-phablet:~$ ps -elf | grep oxide
4 S phablet 9029 8703 0 80 0 - 401 wait 11:37 ? 00:00:00 /usr/lib/arm-linux-gnueabihf/oxide-qt/chrome-sandbox /usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --type=zygote --shared-memory-override-path=/dev/shm/webbrowser-app.oxide --disable-gpu-comphablet@ubuntu-phablet:~$ ps -elf | grep oxide
4 S phablet 9982 9947 0 80 0 - 402 wait 11:42 ? 00:00:00 /usr/lib/arm-linux-gnueabihf/oxide-qt/chrome-sandbox /usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --type=zygote --shared-memory-override-path=/dev/shm/com.ubuntu.developer.webapps.webapp-twitter.oxide --disable-gpu-compositing
4 S phablet 9983 9982 0 80 0 - 33236 wait 11:42 ? 00:00:00 /usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --type=zygote --shared-memory-override-path=/dev/shm/com.ubuntu.developer.webapps.webapp-twitter.oxide --disable-gpu-compositing
1 S phablet 9987 9983 0 80 0 - 33236 poll_s 11:42 ? 00:00:00 /usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --type=zygote --shared-memory-override-path=/dev/shm/com.ubuntu.developer.webapps.webapp-twitter.oxide --disable-gpu-compositing
1 S phablet 10007 9987 9 80 0 - 60568 futex_ 11:42 ? 00:00:00 /usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --type=renderer --enable-overlay-scrollbar --enable-smooth-scrolling --profiler-timing=0 --use-gl=egl --disable-webrtc-hw-encoding --primordial-pipe-token=C7125B46D0FE3D62BD533853BFDF9C58 --lang=en_US --shared-memory-override-path=/dev/shm/com.ubuntu.developer.webapps.webapp-twitter.oxide --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553 --mojo-application-channel-token=C7125B46D0FE3D62BD533853BFDF9C58 --channel=9947.1.48209637 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd

That's normal - there's not really 2 zygote processes, but the zygote process forks early on to run the real zygote, with the parent assuming the role of init in the PID namespace.