View Single Post
Old 02-21-2014, 07:53 AM   #33
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by dsmid View Post
Thanks for your research knc, that makes sense.
However, for me and for the users it's simpler and safer to overwrite framework/pillow files than to overwrite kernel.
OH,
a **practical** solution is desired?

I may be all out of **practical** here.

Like the famous doctor said:
"If it hurts when you do that, stop doing it."

- - - - -

Seriously -
The structures you are running out of are parts in the memory resident section of kernel memory.

So adding swap will not directly help the situation.

But adding swap might reduce the general level of "memory pressure" and in-directly allow more of these structures to exist.

- - - - -

Two "end user friendly" things you may want to do:

Add a BIG RED NOTE to the release post that this add-in may have to be un-installed before doing a firmware update.

Add an "update blocker" to the installation of this package.
Just to reduce the chance of an OTA, "auto-brick" (ah, "update").
knc1 is offline   Reply With Quote