Hi all,
I am working on an industrial computer with touch screen and a Cfast as storage, Atom Cpu dual core 1.6Ghz, 2GB ram. UEFI 2.0 compatible, American Megatrends 4.6.4.1.
TinyCore is version 5.4 all in RAM (version 6.1 does not boot: it stops in the middle).
I launch my java program at startup through the terminal by means of the command:
aterm -e sh -c "cd /home/mybindir && java myprogram" &
The command is put as an executable named "atermbis" under /mnt/sda1/tce.
The java environment is set as "OnBoot".
My program starts as usual. I have a few buttons I have to push sometimes.
Usually it seems working fine, but, after a few minutes (say 5-10) if I push a button that, apart changing the color of the button, does not follow anything, or maybe it does its actions after a while.
If, while waiting for the command acting, I move the cursor just a little, all runs as it should be.
It seems like "postponing" the actions linked to the pressure of the buttom at an indefined time forward.
This happens as with Sun Java (jre 7.07 from repo) as with OpenJdk, so it does not seem linked to the version of java.
This is a very strange thing, because in some ways it seems that sometimes it needs a double pression of the button.
By the way the program was running fine on older machines with slackware on it, showing no such issue.
Looking at processes with "top" the program seems to suck around 34% of VSZ (%VSZ %CPU = 0.0), without spikes, quite constant.
In some ways it is the same thing it was happening with screen saver locking java (as I said on my previous post).
But this machine (the same that came back from customer) has the screen save stopped and java still "sleeping".
Maybe the screensaver was not the one to blame.
Any idea on what I am doing wrong? Is there an issue with java and TinyCore?
Thanx all