We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
I'm periodically now seeing an "Out of Memory" dialog after upgrading to V5.15. Dismissing the dialog causes another to immediately appear. If I continue to dismiss them (usually 5 or 6) I get the "uVision has stopped working" dialog forcing me to restart the IDE. I using the same Windows 7 Ultimate 32-GB RAM machine and these crashes didn't occur before the update to V5.15.
Does "Task Manager" provide any details as to the type of resource leak that's occuring?
Since the Out of Memory/IDE crashes are periodic and I'm under pressure to get my project complete I'd didn't examine the crash more closely. The Task Mgr memory stats for UV4.exe currently are: Working Set 99,192K,Peak Working Set 99,192K, Working Set Delta 0K,Memory(Private Working Set) 76,808K, Commit Size 219,840K, Paged Pool 526K
When/if it goes into Out of Memory again, I'll collect and post those stats. Totalled committed RAM is 9.32 GB out of 32GB.
Just crashed again (uVision has stopped working preceded by Out of Memory dialogs). I was just editing a half dozen source files.
Task Mgr memory stats for UV4.exe: Working Set 1,921,452K, Peak Working Set 1,921,452K, Working Set Diff 0K, Memory (Private Working Set) 1,889,084K, Commit Size 1,904,984K.
Total committed RAM is 14.5GB out of 32GB.
Memory use, obviously, went way up.
With UV4 running and the Task Mgr Processes tab open, I just selected the various source files I was editing to see if would have a visible effect on memory allocation. When I selected one particular file, memory useage began climbing until uVision crashed.
It was a source file created by an old copy of CodeWright and I thought that might somehow relate to the memory allocation problem. However, I created a new file with UV4 and copied the source into it, and the new file causes UV4 to memory crash too. So there must be something about the file's content causing the problem.
I'd be happy to send you the problematic source file if you'd like.
I forgot to mention that closing the errand file before UV4 crashes stops the memory allocation from rising but Does Not release any of the allocated memory. Subsequently opening "safe" files causes additional memory allocations (which deallocate when I close the safe files) but the only way to reset memory allocation to a minimum is to terminate and restart UV4.
Joe, thanks for raising this problem.
It looks like this problem is caused by the integrated compiler that provides Dynamic Syntax Checking. To verify that please disable the option Dynamic Syntax Checking using the Edit - Configuration - Text Completion menu dialog.
It would be great to sent the suspicious file that you mention to our support email: support.intl@keil.com. Please make a reference to this discussion forum thread.
Thanks!
We have received your source file which might cause this problem, but I cannot duplicate this issue. Let's discuss further details in the support case.
Hans Schneebauer Technical Support Group Germany
FYI to anyone tracking this thread. A memory allocation problem with Version 5.15 which results in Out of Memory and, eventually, uVision has stopped working HAS BEEN CONFIRMED and referred to developers in Germany. For now I just open the problem causing code snippet file in another editor and get back to work on my project.