View Single Post
Old 05-09-2012, 05:12 PM   #73
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by cscat View Post
I do remember to receive Segmentation fault too, though I'm not sure if it was before me updating to 5.1.0. Now it runs smoothly.

And by the way, each time I run gmplay, I should restart or do a killall pillowd, because KT becomes unresponsive to Home key. It doesn't matter if I let the animation complete or interrupt it with Ctrl+C. I wonder why! It used to work Geekmaster, in the very first day you released this code (early version of gmplay).
The segfault is usually caused by a buffer overflow or such. The code is very simple. Perhaps I have an "off by one" error that crept into it. If somebody finds a fix please let me know.

Regarding the framework locking up -- I think that happens because I am "dominating" the display and the framework checks for display "not busy" and just "gives up" if it goes to long with eink busy... But I only saw the framework go dead like that once on my K3, and an SSH "framework restart" command fixed it...
geekmaster is offline   Reply With Quote