View Single Post
Old 12-10-2015, 01:19 PM   #137
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
Quote:
Originally Posted by PeterT View Post
GeoffR; when I do the same on my Glo, no problem at all!
Okay, I found that a stack log was created at some point, just not at the time of the initial problem, and I am able to reproduce it consistently on an unpatched device with these steps:

Initial state: No patches, no undocumented FeatureSettings active, wi-fi off, database size 63.7MB, 799 books, 18 sideloaded fonts.

1. Power off and on again (to start with a clean slate)
2. Open a KePub book (I used this one, bought and synced from Kobo)
3. Select Kobo Tsukushi Mincho, Kobo UD Kakugo, OpenDyslexic, Malabar, Amasis
4. Tap home to close the KePub book
5. Open a DRM-free ePub book (I used Timescape by Gregory Benford, 401 pages, no embedded fonts)
6. Select Kobo Tsukushi Mincho font
7 Swipe to turn a page (at this point the book closed and was marked finished)
8. Open the ePub book again (It displays a blank page)
9. Open Aa menu, select Amasis
10. Tap home to close the ePub book

The stack log was produced after step 8 or 9 I think (it is not there after step 7, at least.) Who can I sent it to?
Spoiler:
Code:
OH THE HUMANITY!
pid: 831, tid: 831, rev: 4b76aa47bde1a96892dfaf6721f18f36179d6a2a
  >>> /usr/local/Kobo/adobehost <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
 r0 00000000  r1 3002e028  r2 00eb32c0  r3 00000100
 r4 00011000  r5 f0000400  r6 42555347  r7 b063770b
 r8 d8330400  r9 00000001  10 30ee2008  fp 00000000
 ip 3a210300  sp 7ee93964  lr 322f534f  pc 2d7f82c0  cpsr 200d0010
    #00 sp: 0x7ee93964 ip: 0x2d7f82c0  /lib/libc-2.11.1.so: memcpy+0x50
--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
pid: 831, tid: 832
 r0 fffffdfe  r1 2fc22d18  r2 00000000  r3 00000000
 r4 00000000  r5 2fc22d17  r6 00000040  r7 0000008e
 r8 2c9ceb98  r9 00000001  10 2fc22d18  fp 00000006
 ip 00000000  sp 2fc22cf0  lr 2d829838  pc 2d829848  cpsr 80000010
    #00 sp: 0x2fc22cf0 ip: 0x2d829848  /lib/libc-2.11.1.so: __select+0x48
    #01 sp: 0x2fc22d00 ip: 0x2c7d2fbb  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN9QLockFile6unlockEv+0xf16
    #02 sp: 0x2fc22dc0 ip: 0x2c6b0229  /usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2: _ZN7QThread21setTerminationEnabledEb+0x210
    #03 sp: 0x2fc22de8 ip: 0x2d655ed3  /lib/libpthread-2.11.1.so: start_thread+0xa6



Edit: To explain, I don't think opening the KePub is related to the problem, it is just an easy reproducable way of allocating some resources to simulate the state the device would be in after a bit of ordinary use.

Edit2: The stack log is not produced if I remove my sideloaded fonts, but the problem remains unchanged. I've sent the info to a Kobo representative.

Last edited by GeoffR; 12-10-2015 at 07:08 PM. Reason: ... if I remove my sideloaded fonts ...
GeoffR is offline   Reply With Quote