Quote:
Originally Posted by EastEriq
Motivated by this post
If I log in with ssh, I for example see with top that the process
Code:
{reader.lua} ./luajit ./reader.lua
is taking 407Mb, 87% of VSZ on a particular medium sized epub, though I have still 157Mb free. Too much for headroom?
[/URL], but it's old |
PB631 (and all old models for that matter) is skirting the line with memory. I'll try to run with ulimit to try simulate your situation, but overall it doesn't look good - koreader is a massive memory hog.
Also, does the nightly crash straight away during startup (ie bug on my end), or after doing a bit of stuff for a while (= out of memory)?
As for how to debug, indeed there's useable gdb inside. ssh in, set up your environment by pasting the following:
Code:
export LC_ALL="en_US.UTF-8"
export KOREADER_DIR=/mnt/ext1/applications/koreader
export LD_LIBRARY_PATH=${KOREADER_DIR}/libs
export KO_EXIT_CODE="/tmp/.koreader.exit"
export TESSDATA_PREFIX="data"
export STARDICT_DATA_DIR="data/dict"
cd $KOREADER_DIR
And then you can:
Code:
$ gdb ./luajit
...
(gdb) handle SIGILL pass nostop noprint
(gdb) r reader.lua -d