ConnorDY/OSRS-Environment-Exporter

[BUG] Program crashes on Mac after clicking 'Launch' with 'trace trap' error.

mattgates opened this issue · 6 comments

  • [ x] I am using the latest version of the exporter

Bug description

When I run the program, select a cache, and press 'Launch', the following error happens.
image
If the program does run (happened once out of maybe 50 attempts) then the window is grey and I am still able to select chunks and export. I will update this issue with an image if I can get it to load again. I have tried downloading and using the five most recent caches.

Steps to reproduce

MacOS 13.1 on an M1 Pro
Java versions in screenshot of Terminal above.

  1. Execute ./run in the directory of the extraction.
  2. Select a downloaded cache.
  3. Click 'Launch' and program crashes.

The current behavior

A crash report window opens after running ./run and zsh: trace trap ./run is found in Terminal. The crash report has been attached to this issue.
crash_log.txt

The expected behavior

The program loads and I can see the game environment.

I'm having this same issue on an M1 mac laptop

And actually I'm also having the issue on my x64 mac desktop

I'm not too sure on how to go about solving this just yet, but please can you try ./run --no-preview or equivalent for whichever command you normally run it with? I suspect it's the 3d preview that's crashing it but I don't know why. If you run it without the preview it will of course be much more limited in its functionality but it should still export correctly, and will give us the certainty that it is the 3d component crashing and not something else.

@ConnorDY also if you have time can you check what os version and hardware your mac has, assuming it hasn't suddenly stopped working for you?

That worked perfectly actually thanks!! Must be the 3d previewer. You guys are amazing man this is too cool

I can also confirm that running it with --no-preview worked fine on my machine.

One more thing I'd be interested to hear about is if passing -XstartOnFirstThread to the java command (i.e. before the -jar) makes a difference. It likely won't, since the opengl canvas starts on the AWT thread, but it's another thing that's worth a try