2025-10-04 1:49 AM
Worth checking this on whatever new version comes out. This is really sloppy Java code, which is something ST tend to not fix (see the random file opening bug for example).
It is about 10k bytes per second.
Probably not noticed by most people, using this feature only occassionally.
For long term debug you will probably be using either a UART or USB VCP.
2025-10-08 2:35 AM - edited 2025-10-08 3:17 AM
Hello @PHolt.1
I'm currently checking this issue. I will get back to you asap.
Could you please provide more details about your operating system and the version of STM32CubeIDE you are using?
THX
Ghofrane
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-10-08 5:25 AM - edited 2025-10-08 5:26 AM
All versions do it.
Especially if PC Sampling is enabled (to get statistical profiling).
It runs for about an hour, maybe, before it reached 1.5GB and crashes.
Same with STLINK V3 in normal mode, OpenOCD mode, and with a Segger V9 box, so it isn't related to the debugger itself.
Note that Cube has no proper error handling on the debugger USB interface, so a debugger with a funny USB issue will mess up Cube. Had that once.
Win7-64 and Win10.
This is Cube heading towards 1.5GB (normally ~700MB)
2025-10-08 6:47 AM
Hello @PHolt.1
Thank you for your contribution. Our development team is currently investigating this behavior under internal ticket 176927.
I will keep you posted with updates.
THX
Ghofrane
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.