> On 5 Jul 2016, at 14:25, Dmitry Markman <dmark...@mac.com> wrote: > > you’re right > > our problem isn’t clang malloc optimization > > it looks like it’s more related to memory overcommitment >
Perhaps - how much memory are you actually using at any one time? Some gross testing with top before the crash might show you if you are actually running out of physical ram. If you are then there may be a difference in the way the memory you’ve requested is later allocated to physical ram between the various OSes. > unfortunately we didn’t see any dialog you described, application just crashed Do you have a crash log? Should be one somewhere, Xcode can find them, sometimes. Your best next step is to find that and see what it’s telling you about the crash. > > what was confusing that debug build isn’t failing, only release build of our > library crashes application Perhaps you have a memory smashing bug which only shows up in release mode. clang compiles differently so it can uncover things gcc doesn’t, and vice-versa. _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
