This question is locked. New answers and comments are not allowed.
I searched previous threads for this issue so I hope that this is novel.
After a number of code, run and debug iterations using Graphite on my 32-bit Windows machine, I begin to encounter synching and debugging issues where changes to the sources do not show up correctly when viewed through the integrated debugger in the simulator. To correct this problem, I re-start the IDE.
Frequently during these restarts, I see one or several Icenium Graphite processes still running and having a memory footprint typically ranging from 50K to 400K each. If I kill these ghost / orphaned processes before restarting the IDE, the sync issues with the debugger go away. It seems that whatever the circumstance that permits these additional Graphite processes to exist, that they compete with the project and debugger sync mechanism (which may involve the cloud sync).
I'm not sure that there is anything immediate that can be done, but I wanted to bring this to your attention.
Thank you.
After a number of code, run and debug iterations using Graphite on my 32-bit Windows machine, I begin to encounter synching and debugging issues where changes to the sources do not show up correctly when viewed through the integrated debugger in the simulator. To correct this problem, I re-start the IDE.
Frequently during these restarts, I see one or several Icenium Graphite processes still running and having a memory footprint typically ranging from 50K to 400K each. If I kill these ghost / orphaned processes before restarting the IDE, the sync issues with the debugger go away. It seems that whatever the circumstance that permits these additional Graphite processes to exist, that they compete with the project and debugger sync mechanism (which may involve the cloud sync).
I'm not sure that there is anything immediate that can be done, but I wanted to bring this to your attention.
Thank you.
1 Answer, 1 is accepted
0
Hi Joseph,
Thanks for letting us know of this problem.
Regards,
Steve
Telerik
Do you enjoy Icenium? Vote for it as your favorite new product here (use short code H048S).
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
Thanks for letting us know of this problem.
We see you're using Windows XP machine, can you confirm you have SP3 installed on it? Also please go through the Windows Event Viewer for any logs that might indicate a problem with Graphite and if there are any, please export them and provide a link (or save them as .txt and attach here).
Another thing to try is wipe clean the Graphite installation in case it got corrupted somehow. Before you start Graphite, try the following steps:
- Close all Icenium Graphite instances. Open the Task Manager and make sure that there are no running processes with the name Icenium.Graphite.exe. If there is - kill it.
- Uninstall Graphite.
- Delete all contents in the %localappdata%\Temp\IceDeviceSimulator folder.
- Delete all contents in the %localappdata%\Telerik\BlackDragon\ folder.
- Delete all contents in the %localappdata%\Apps\2.0 folder.
- Re-install Graphite.
Regards,
Steve
Telerik
Do you enjoy Icenium? Vote for it as your favorite new product here (use short code H048S).
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.