1 Could we compile it out of 1.5.4 ?
2 Can we print assertions to standard error instead of popping up a dialog box on windows? Its really really annoying.
3 Can we fix it the right way? Its tied to the loaded of cached bam files because removing those fixes the problem. Assertion happens only on model and texture load calls.
It’s already compiled out in 1.5.3. You must be using 1.5.2 or earlier.
Most assertions actually raise a Python exception, but this is extremely low-level code, which appears before we’ve even defined the mechanism to interface to Python, so all it can do is fall back to the system assert() call, which does whatever it does. By design, though, an assertion is not supposed to be triggered. It is of course a bug that this one keeps coming up; it’s a bug that we haven’t solved yet.
If you have the right solution I’d be happy to apply it. In the meantime, we’ll have to leave it commented out. It doesn’t seem to cause major problems with the check commented out (it just means the pstats memory reporting goes wonky sometimes).