Skip to main content

phoneme stops responding after some time

4 replies [Last post]
tusharj9
Offline
Joined: 2005-09-22

Hi,
I have compiled phoneme feature on linux i386 in MVM mode. It is now giving strange problem after I compiled it with directFB support. It stops responding after some time (randomly) . if some activity is performed like launching of midlet and continues interaction with midlet it won't hang .But after the interaction is stopped it stops responding .
Is it some how related to native event handling?

regards,
tushar

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
aap031
Offline
Joined: 2006-10-18

Hi Tushar,

Can you tell if it unfreezes randomly as well? Say in next 5-10 minutes after it got stopped responding

Thanks,
Andrey

tusharj9
Offline
Joined: 2005-09-22

Hi Andry ,
Ya some time it will respond to your key press events after very long time in unpredictable way.
I'm checking mastermode_check_events.c and trying some hacks if it works.
I have ported vm for slave mode in which after some hacks in checkForAllSignals() to check for infinite looping i'm able to stop freezing of vm . But same thing is not working for master mode.

Any clues ?

Regards,
Tushar

aap031
Offline
Joined: 2006-10-18

I've seen the similar thing in master mode compiled in frame buffer in conjunction with qvfb. However I discovered that at exactly the same time there are problems with some other X applications on the same machine. So I thought it was caused by X/Qt interoperability issues. As you tell you are using directFB this might have been wrong assumption

Do you know where the execution point is when the thing freezes?

Thanks,
Andrey

tusharj9
Offline
Joined: 2005-09-22

Hi Andrey
I got the pain point.
Scheduler.cpp send timeout (sleep time) of -1 when there is no active running thread.
For my case when inside checkForSystemSignal() it calls adjustTimeout , adjustTimeout keeps timeout unaltered to -1. This -1 time out value when reaches to checkForAllSignals () , it goes in infinite while loop because all loop breaking condition expects timeout value zero or greater.

After setting timeout value properly in adjustTimeout , things are working smoothly.

So for my case peek_timer() returns null value inside adjustTimeout() for timer handle. Is adjustTimeout need to fixed to handle this condition or is there any problem with my phoneME port ?

Reg,
Tushar