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.