Nick ODell

Nope, never figured it out. It does look like a similar problem, though. In each stack trace, there's a malloc being called from a graphics driver. Maybe the problem is...

Here's a stacktrace from a recent version. (5aefd7b) Unfortunately, I seem to have lost the scripts I was using for gdb. ``` Studio: malloc.c:2406: sysmalloc: Assertion `(old_top == initial_top (av)...

This is running in Studio. I'll use a debugger and get back to you.

The bad_alloc error occurs on the line `a.exec();` in `gui/src/main.cpp`. I captured the state of the variable a on a failed run and a successful run. successful run: ``` Thread...

__cxa_throw backtrace: ``` #0 0x00007ffff5c42260 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #1 0x00007ffff5fc59b2 in qBadAlloc() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x00007ffff6043bba in QListData::detach(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x00007ffff5fef4de in ?? () from...

That's looking really good. Looks like you squashed the bad_alloc bug entirely. :D After that revision, I have a 94% success rate in starting the program. rev effd24e: ``` success:...

On the subject of ao-test, I have 2 failures. Maybe they're related to the remaining problems: ``` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ao-test is a Catch v1.1 b3 host application. Run with -? for...

I'll try to get a backtrace of the other errors. I'll need to figure out how to script gdb first - I don't want to manually run ao 1000 times....

Here's a sysmalloc trace: ``` Studio: malloc.c:2406: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end...

In general, fork() is [very broken on OSX](https://bugs.python.org/issue33725), so this issue might be caused by that. Can you look at Console.app and include the traceback, per the instructions in #75...