Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Reply
Developer
Posts: 61
Registered: ‎12-31-2010
My Device: 9800
My Carrier: Airtel
Accepted Solution

Blackberry 7 simulator fledge.exe not exit in the task manager

I am not able to exit the fledge.exe from the system taskmanager processes it showing 50% of cpu usage.

R33
Developer
Posts: 16,851
Registered: ‎07-29-2008
My Device: Z10 LE, Z30, Passport
My Carrier: O2 Germany

Re: Blackberry 7 simulator fledge.exe not exit in the task manager

you should be able to kill any process you want with the task manager
----------------------------------------------------------
feel free to press the like button on the right side to thank the user that helped you.
please mark posts as solved if you found a solution.
@SimonHain on twitter
Developer
Posts: 61
Registered: ‎12-31-2010
My Device: 9800
My Carrier: Airtel

Re: Blackberry 7 simulator fledge.exe not exit in the task manager

i tried by using task manager. But its not killing the process.


simon_hain wrote:
you should be able to kill any process you want with the task manager

 

R33
Developer
Posts: 61
Registered: ‎12-31-2010
My Device: 9800
My Carrier: Airtel

Re: Blackberry 7 simulator fledge.exe not exit in the task manager

even the simulator is not working. its stopping after its loaded 70%
R33
Highlighted
Developer
Posts: 19,633
Registered: ‎07-14-2008
My Device: Not Specified

Re: Blackberry 7 simulator fledge.exe not exit in the task manager

I had this happen to me recently.  Simulators that worked perfectly before stopped loading with the bar at about 70%.  I tried cleaning, deleting and reinstalling, and then did a system restore to be fore the last set of Microsoft updates.  This seemed to fix the problem and then applying the updates worked fine and the Simulators continue to work.  Go figure. 

 

If I was to point the finger at something, I think at that specific point it is trying to establish connections, for example with the debugger.  My suspicion is there is some sort of communication issue. 

 

Sorry can't be more helpful.