STM32CubeIDE keeps crashing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-27 1:53 AM
I was using STM32CubeIDE version 1.16. It was crashing occasionally. Then I wanted to update to version 1.18. It started to crash constantly while updating. Then I cleaned the program with all its extensions and reinstalled the new version(1.18). But the problem was not solved and it keeps crashing.
I checked the form and your answers. I couldn't find any solution for this.
Below is a screenshot of the errors I receive.
 
Solved! Go to Solution.
- Labels:
-
STM32CubeIDE
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-27 1:25 PM
Which version of FortiEDR do you have? In any case this thing is managed remotely by your IT. Please report to them and they know how to investigate.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-27 2:16 AM
Can you supply more information? What exact operating system are you using? What do you mean by "cleaned the program"?
Click "Accept as Solution" if a reply solved your problem. If no solution was posted please answer with your own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-27 2:35 AM
I am using Windows 11. I uninstalled and reinstalled STM32CubeIde. I tried the last 3 versions, but in all of them the program suddenly closes after a while.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-27 3:30 AM - edited ‎2025-03-27 3:34 AM
Do you have a virus scanner running? Do you have any background programs running? Do you have other programs that crash or is this the only program that gives issues?
I assume you have restarted windows.
Click "Accept as Solution" if a reply solved your problem. If no solution was posted please answer with your own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-27 4:03 AM
Yes, FortiEDR was active. I disabled it. The program remained open for a longer time, but after 1 hour it crashed again with the same error.
I don't have any other program that crashed, only cubeide.
Yes, I restarted it many times.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-27 5:54 AM - edited ‎2025-03-27 5:56 AM
@sahiinbeyza wrote:Yes, FortiEDR was active. I disabled it. The program remained open for a longer time, but after 1 hour it crashed again with the same error.
Now we are getting somewhere. Perhaps there is a memory leak (that occurs only on your system for some reason). Can you periodically check the memory usage in task manager? And once it crashes also check memory usage before closing. If it keeps growing that's a sign of a memory leak.
I checked and my STM32CubeIDE 1.16 uses between about 800 and 1600MB.
Perhaps you will notice under what circumstances the memory usage spikes (compiling?). Maybe it only happens with one specific project? Maybe it's a combination of settings of your workspace?
Click "Accept as Solution" if a reply solved your problem. If no solution was posted please answer with your own.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-27 1:25 PM
Which version of FortiEDR do you have? In any case this thing is managed remotely by your IT. Please report to them and they know how to investigate.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2025-03-27 10:47 PM
IT completely disabled the firewall for the STM32CubeIDE application on FortiEDR and the problem was solved. As you said at the beginning, it was actually caused by the virus scanner application :)
Thank you..
