Topic : Ride crashes after several debug cycles

Forum : ARM

Original Post
Post Information Post
December 3, 2010 - 9:16am
Guest

Hello,

i have a repeatable problem with Ride.
I have a project of type "Debug Application". After starting Ride and loading the project Ride occupies about 100MB of memory. When i now press the "Start debugging" button the memory footprint of Ride increases to approx. 440MB between the message box "Initialising emulator" and "Programming flash". Now i terminate debug but the memory footprint stays at 440MB. With every new "Start debug" Ride allocates additonal 300MB of memory. After the 7. cycle Ride crashes because the memory footprint goes over the 2GB ram size in my PC.

Ride 7.30.10.0159 with patch 7.30.10.0169
RKit -ARM 1.26.10.0130

I have sent the error report from Ride after the crash.

Regards,

Christian

PS: If needed i have prepared this project without source code so that the problem can be reproduced.
Replies
Post Information Post
+1
0
-1
December 3, 2010 - 8:28pm
Guest

I see the similar behaviour, but not quite as aggressive. Mem usage rockets up to ~400MB, then subsequent sessions grow by ~48MB.
+1
0
-1
December 10, 2010 - 1:59pm
Guest

Hello,

can please someone from Raisonance comment on this? Is the bug recognised? Will there be a fix?

Regards,
Christian
+1
0
-1
December 10, 2010 - 3:48pm
Raisonance Support Team

Hi,

There may be a problem due to an unhandled error while in a debug session. In this case, subsequent uses of Ride7 tend to take more and more memory up to crashes.

The first solution is to make sure you are using the latest Ride7 version (from http://www.mcu-raisonance.com/mcu_downloads.html)

You can then remove all Ride7 intermediate files:
- Close all instances of RidE7 and RFlasher7
- Navigate to your project directory
- Erase all files except your project files (.c, .h, .asm), your .rapp and .rprj files.

Restart Ride7, problem should be fixed.

Note that this problem has been fixed in recent versions of Ride7.

Best Regards,
+1
0
-1
December 10, 2010 - 3:59pm
Guest

Hi Bruno,

thank you for the reply.

The versions i use are the latest. The version numbers are in my first post.

I have tried your suggestion and deleted all files except .rapp and .rprj.

No success. Memory footprint after starting Ride and loading the project is ~100MB, after starting debug ~470MB and after second time starting the debug ~800MB.

I can provide my project if neccessary.

Best regards,
Christian
+1
0
-1
December 10, 2010 - 5:18pm
Raisonance Support Team

Hi,

Please first check if your problem is the same as (or related to) this other one:
http://forum.raisonance.com/viewtopic.php?pid=11585#p11585

Try the fix there and if it still doesn't solve the problem, please send us (support@raisonance.com) your project. (including source and header filess, precompiled object files, listing files, etc. just zip your project's folder)

Best Regards,

Vincent
+1
0
-1
December 13, 2010 - 9:42am
Guest

Hi,

i have tried the patch but it does not change the behaviour of Ride in my case.

I send you the project for inspection. At this point i only send you the elf file and the project files. Sending the source code is problematic for me, but the memory issue is repeatable with only the elf file.

Regards,
Christian
+1
0
-1
December 13, 2010 - 5:37pm
Raisonance Support Team

Hi,

This discussion has been continued by email and the problem was identified and solved.

The next version of the RKit-ARM (1.30...., due in the coming weeks) will include the correction.

If other customers have an urgent need of the fix, please request it by email. (support@raisonance.com)

Many thanks to chprash for his patience and detailed feedback.

Best Regards,

Vincent