View Single Post
Old 10-16-2024, 01:31 PM   #982
mergen3107
Wizard
mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.mergen3107 ought to be getting tired of karma fortunes by now.
 
mergen3107's Avatar
 
Posts: 1,507
Karma: 5000046
Join Date: Feb 2012
Location: Cape Canaveral
Device: Kindle Scribe
I found in /usr/bin/dump-stack that you can drop and empty file called DISABLE_CORE_DUMP in the main visible root (/mnt/us/) to stop Kindle from making core dumps (KPPMain, powerd, cmd, and possible others).

As far as I understood, this JB method requires this specific file in in the system root (/PRE_GM_DEBUGGING_FEATURES_ENABLED__REMOVE_AT_GMC) to be present in order for JB to work. This, in turn, makes Kindle a dev test device. Therefore, stack is dumped upon several actions, most of them are actually regular actions.

I tried it on Kindle Scribe, both on FW 5.16.2.0.1 and 5.16.21 (hardfloats, hf), and it worked both times. No more core dumps.

Only occasional things I still get is from Indexer, it dumps some archive and summary of what was indexed in /mnt/us/documents. But at least these are a few hundred KBs, and not 200-300 MB that core dumps were used to be. Most of the times it is when I exit KOReader that was launched in "no framework" mode.

This method is the least intrusive, and it doesn't seem to break anything big time. I can still browse Kindle store, read books, etc.
mergen3107 is offline   Reply With Quote