When running Cider, an F6 launches the simulator.
If you click on cider and start editing without closing the Corona simulator, Cider can become unresponsive & lock up.
An option to stop simulator when typing would solve this.
Thus if it is getting output and the user starts editing a file, immediately kill the simulator.
Or - at least ignore it while editing. [import]uid: 13784 topic_id: 26786 reply_id: 326786[/import]
Hello Marble,
Thanks for the report and thanks for starting a new thread.
How often does this occur? We tried to replicate the problem and it didn’t happen. What else are you running? Is the memory/cpu timeline running as well?
Regards,
M.Y. Developers
[import]uid: 55057 topic_id: 26786 reply_id: 108852[/import]
It happens after some usage. I have a *LOT* of output going on that I watch. Basically, each function call says something like print (“this function called”)
[EDIT] By some usage, that means it can vary. It really depends on how many edits I’m doing and how quickly I’m going back and forth between the code & the simulator.[EDIT]
I am on Win7 ultimate 64bit, 6GB of RAM, i7 Q720 @ 1.6Ghz
CPU utilization is around 0 - 15%
RAM utilization is around 3.4 GB
I have not been using the MemoryTimeline plugin.
This happens usually after several runs and edits.
My main body of code is over 3000 lines (and growing).
[import]uid: 13784 topic_id: 26786 reply_id: 109419[/import]
(also posted on the main thread)
Are you still having these problems? Please let us know. Is the 3gb figure from the task manager? It would help us tremendously if you could send us an email so we can show you how to do a visual VM profiling session you can have running in the background to measure the memory footprint as you use Cider. That would help us a lot.
Regards,
M.Y. Developers [import]uid: 55057 topic_id: 26786 reply_id: 110096[/import]
Yes, it was from task manager. The 3GB usage was total, not Cider specifically. [import]uid: 13784 topic_id: 26786 reply_id: 110174[/import]