after updating to portage 2.2-rc1 I tried to install oo-bin it resulted in cpu going 100% . Impossible to stop from command line , I even shut everthing down to login console but the rouge process was still runnning and did not respond to kill -9 the wild process looked like this: 6478 pts/0 RN 2:12 python /usr/lib/portage/bin/filter-bash-environment.py ????DIRSTACK EUID FUNCNAME GROUPS???PIPESTATUS PPID SHELLOPTS UID D EBUIL terminal output from portage was this: Traceback (most recent call last): File "/usr/lib/portage/bin/filter-bash-environment.py", line 113, in <module> re.compile(var_pattern), file_in, file_out) File "/usr/lib/portage/bin/filter-bash-environment.py", line 80, in filter_bash_environment file_out.write(line) IOError: [Errno 28] No space left on device Impossible to tell from that message what device caused the error (how about a more explicit error??), no partition was 100% when I got back controll. However, the trigger of this bug (and regression since 2.1.5.6 succeeds) would seem to be low disk space on root. There was 1.1GB on portage partition (which includes portage tmpdir). What ever the cause it clearly should not throw an unstoppable process at 100% CPU and force a reboot. Reproducible: Always
Interesting marking this as normal without any comment. I would have thought a runaway process the requires reboot would fit the description of Critical.
Where you really able to produce this runaway process issue more than once? Considering that the process couldn't be killed with kill -9, sounds more like a crashing kernel than a portage bug. Could you reproduce it after a reboot? That "IOError: [Errno 28] No space left on device" error occurred while writing to $T/environment which is always under $PORTAGE_TMPDIR.
I think we can assume there was something else more than portage causing problems here.
