Random crashes in release builds

General JUCE discussion
1

Users are reporting lots of crashes in release builds, but I’m just not seeing them. So I enabled crash dumps for my app. I’ve gotten one back so far and the call stack looks like this:

ntdll.dll!_RtlpCoalesceFreeBlocks@16()  + 0x124e bytes	
ntdll.dll!_RtlFreeHeap@12()  + 0x91f bytes	
MyApp.exe!free(void * pBlock=0x0719d498)  Line 110	C
MyApp.exe!juce::Image::~Image()  + 0xf bytes	C++
MyApp.exe!juce::Image::`vector deleting destructor'()  + 0x8 bytes	C++
MyApp.exe!juce::MenuItemInfo::~MenuItemInfo()  + 0x57 bytes	C++
MyApp.exe!juce::PopupMenu::clear()  + 0x23 bytes	C++
MyApp.exe!juce::PopupMenu::~PopupMenu()  + 0x35 bytes	C++
MyApp.exe!juce::MenuItemInfo::~MenuItemInfo()  + 0x3f bytes	C++
MyApp.exe!juce::PopupMenu::clear()  + 0x23 bytes	C++
MyApp.exe!juce::PopupMenu::~PopupMenu()  + 0x35 bytes	C++

I’m guessing this means the heap got previously corrupted. Anybody have any other ideas to what it could mean?

2

Hmm. PopupMenu manages all its internal objects so it’s unlikely to be a problem in the menu code. I’d agree that it must have been something getting corrupted previously - almost certainly by whatever menu function they just invoked.

It’s a nightmare when people get crashes you can’t reproduce… you have my sympathy!