SIGSTOP when running larger task

[Moxinilian]

Bug Description

When asking Mojo to render a (moderately) higher resolution Mandelbrot set on the SaaS playground, the process gets killed with SIGSTOP.

Steps to Reproduce

1. Load the Mandelbrot set example
2. Set the xn and yn values to

alias xn = 450*4
alias yn = 375*4

3. Run the snippets up to the plotting code

Context

11:freezer:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
10:pids:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
9:hugetlb:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
8:net_cls,net_prio:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
7:blkio:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
6:cpu,cpuacct:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
5:cpuset:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
4:devices:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
3:perf_event:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
2:memory:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
1:name=systemd:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pode1d9699f_1da3_4328_b360_63147b8b29e8.slice/cri-containerd-1a8ccbfcaad7998d860b64649a3ad7e4f6f2c676694847e674ec2ae03b618b20.scope
0::/

[HelifeWasTaken]

Isn't that just the kubernetes pod that has limit to CPU and memory ?

[ZolotukhinM]

This should be fixed in the next update, please stay tuned!