lavavu/LavaVu

OSX bug

Closed this issue · 6 comments

jmansour commented

Hi Owen

On OSX, when running 1_07_SlabSubduction I'm encountering this:

$ cd docs/examples
$  ../../utils/ipynb_to_py.sh 1_07_SlabSubduction.ipynb
$ lldb -- python 1_07_SlabSubduction.py
(lldb) target create "python"
Current executable set to 'python' (x86_64).
(lldb) settings set -- target.run-args  "1_07_SlabSubduction.py"
(lldb) run

...

In func SystemLinearEquations_NonLinearExecute: Converged after 9 iterations.
Process 28861 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x1c00)
    frame #0: 0x00007fff38c728ed GLEngine`gleRunVertexSubmitImmediate + 5965
GLEngine`gleRunVertexSubmitImmediate:
->  0x7fff38c728ed <+5965>: movq   (%r12), %rax
    0x7fff38c728f1 <+5969>: movq   %rax, -0xf8(%rbp)
    0x7fff38c728f8 <+5976>: jmp    0x7fff38c73b70            ; <+10704>
    0x7fff38c728fd <+5981>: movq   (%r12), %rax
Target 0: (python) stopped.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x1c00)
  * frame #0: 0x00007fff38c728ed GLEngine`gleRunVertexSubmitImmediate + 5965
    frame #1: 0x00007fff38bf05d2 GLEngine`glDrawElements_IMM_Exec + 1155
    frame #2: 0x00000001088f3aa5 libLavaVu.dylib`FontManager::rasterPrintString(char const*) + 437
    frame #3: 0x00000001088f2f8c libLavaVu.dylib`FontManager::rasterPrint(int, int, char const*) + 76
    frame #4: 0x00000001088bcba5 libLavaVu.dylib`ColourMap::draw(Session&, Properties&, int, int, int, int, Colour&, bool) + 16101
    frame #5: 0x00000001089b0541 libLavaVu.dylib`View::drawOverlay() + 3153
    frame #6: 0x00000001089492e1 libLavaVu.dylib`LavaVu::drawSceneBlended(bool) + 433
    frame #7: 0x000000010894886a libLavaVu.dylib`LavaVu::display(bool) + 618
    frame #8: 0x000000010896f8d1 libLavaVu.dylib`OpenGLViewer::display(bool) + 689
    frame #9: 0x000000010896fa18 libLavaVu.dylib`OpenGLViewer::outputON(int, int, int, bool) + 40
    frame #10: 0x000000010896ff0f libLavaVu.dylib`OpenGLViewer::image(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, int, bool, int, int) + 431
    frame #11: 0x000000010894f053 libLavaVu.dylib`LavaVu::image(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, int, int, int, bool) + 275
    frame #12: 0x0000000108851472 _LavaVuPython.so`_wrap_LavaVu_image(_object*, _object*) + 5250
    frame #13: 0x00007fff38e3580f .Python`PyEval_EvalFrameEx + 5099
    frame #14: 0x00007fff38e34232 .Python`PyEval_EvalCodeEx + 1551
    frame #15: 0x00007fff38e3a2b4 .Python`___lldb_unnamed_symbol1476$$.Python + 290
    frame #16: 0x00007fff38e34b45 .Python`PyEval_EvalFrameEx + 1825
    frame #17: 0x00007fff38e34232 .Python`PyEval_EvalCodeEx + 1551
    frame #18: 0x00007fff38e3a2b4 .Python`___lldb_unnamed_symbol1476$$.Python + 290
    frame #19: 0x00007fff38e34b45 .Python`PyEval_EvalFrameEx + 1825
    frame #20: 0x00007fff38e34232 .Python`PyEval_EvalCodeEx + 1551
    frame #21: 0x00007fff38e3a2b4 .Python`___lldb_unnamed_symbol1476$$.Python + 290
    frame #22: 0x00007fff38e34b45 .Python`PyEval_EvalFrameEx + 1825
    frame #23: 0x00007fff38e34232 .Python`PyEval_EvalCodeEx + 1551
    frame #24: 0x00007fff38e33c1d .Python`PyEval_EvalCode + 32
    frame #25: 0x00007fff38e52ad1 .Python`___lldb_unnamed_symbol1600$$.Python + 49
    frame #26: 0x00007fff38e52b78 .Python`PyRun_FileExFlags + 130
    frame #27: 0x00007fff38e526fa .Python`PyRun_SimpleFileExFlags + 706
    frame #28: 0x00007fff38e6396c .Python`Py_Main + 3064
    frame #29: 0x00007fff56436015 libdyld.dylib`start + 1

Other models are running fine, so not exactly sure what's triggering this. Have a looksy whenever you get a chance. Thanks!

OKaluza commented

Hey @jmansour it seems to be fixed with the latest development version on the test Mac, so I packaged up a new release (1.2.41). Let me know if it fixes it for you!

jmansour commented

Hey man. I tried it out, and the original issue seems to be fixed, but particle rendering appears to be broken. It looked like the issue you encountered when you were fixing it last week.

jmansour commented

That's the first image from the 1_06 rt model.

OKaluza commented

Thanks John, should be fixed now! Just updated pip package.

jmansour commented