-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 155 #7
Comments
Although "Error 155" causes a centralized kernel panic, it is not really an error but I feature and the process is aborted by a higher rank process as expected. Please reconsider not spawning a new thread without full permissions, thread gets isolated in its own virtual space, and no communication, or exchanges out of its own virtual space is possible, boundaries seem very tight. After using 'cat' command to see the logs, I am really fed-up of the many warnings, info, and threats triggered by the process. From now on I am disregarding any side effect. |
There must be some way to get around the kernel panic and get those full permissions. I am proposing a system shutdown. We definately need to get some kernel updates, this spawned process deserves more permissions. |
"get around", "deserves"?, "shutdown"... definetely, You will make Linus angry in the monthly newsletter! |
Thank you all for assfisting me on these delicate matters. I would've attibuted this 155 kernel panic to a garbage collector overflow. Let's better wait 'till Monday, when a scheduled reboot will take place. |
No description provided.
The text was updated successfully, but these errors were encountered: