#Bash, 4 bytes
Bash, 4 bytes
0ドル&$
Outputs ./forever2.sh: line 1: $: command not found continuously.
Because 0ドル is backgrounded, each parent dies after the invalid command $, and so stack/memory is not eaten up, and this should continue indefinitely.
Strangely the output gets slower and slower over time. top reports that system CPU usage is close to 100%, but there are memory- or CPU-hog processes. Presumably some resource allocation in the kernel gets less and less efficient.
#Bash, 4 bytes
0ドル&$
Outputs ./forever2.sh: line 1: $: command not found continuously.
Because 0ドル is backgrounded, each parent dies after the invalid command $, and so stack/memory is not eaten up, and this should continue indefinitely.
Strangely the output gets slower and slower over time. top reports that system CPU usage is close to 100%, but there are memory- or CPU-hog processes. Presumably some resource allocation in the kernel gets less and less efficient.
Bash, 4 bytes
0ドル&$
Outputs ./forever2.sh: line 1: $: command not found continuously.
Because 0ドル is backgrounded, each parent dies after the invalid command $, and so stack/memory is not eaten up, and this should continue indefinitely.
Strangely the output gets slower and slower over time. top reports that system CPU usage is close to 100%, but there are memory- or CPU-hog processes. Presumably some resource allocation in the kernel gets less and less efficient.
#Bash, 4 bytes
0ドル&$
Outputs ./forever2.sh: line 1: $: command not found continuously.
Because 0ドル is backgrounded, each parent dies after the invalid command $, and so stack/memory is not eaten up, and this should continue indefinitely.
Strangely the output gets slower and slower over time. top reports that system CPU usage is close to 100%, but there are memory- or CPU-hog processes. Presumably some resource allocation in the kernel gets less and less efficient.