Citra not running

Citra Support
1

Issue:
Enter a description of your issue here, in full detail.
It was running fine until I updated it, Now it just gives this in the terminal.
Bharaths-MacBook-Pro:~ Bharath$ /Applications/Citra/nightly/citra-qt.app/Contents/MacOS/citra-qt-bin ; exit;

dyld: Symbol not found: __ZdlPvSt11align_val_t

Referenced from: /Applications/Citra/nightly/citra-qt.app/Contents/MacOS/citra-qt-bin (which was built for Mac OS X 10.13)

Expected in: /usr/lib/libc++.1.dylib

in /Applications/Citra/nightly/citra-qt.app/Contents/MacOS/citra-qt-bin

Abort trap: 6

logout

Saving session…

…copying shared history…

…saving history…truncating history files…

…completed.

System Information

  • Operating System: Mac OS sieraa
  • CPU:
  • GPU:
  • Citra Version (found in title bar):
  • Game:
  • Screenshot of Issue (include the full Citra window including titlebar):

Diagnostic Log
Upload your log file as an attachment by dragging & dropping.

In order to save a copy of the log, follow this guide:
https://community.citra-emu.org/t/how-to-upload-the-log-file/296

2

In order for us to provide better support, we need to see the log generated by Citra. This guide will walk you through how you can obtain the log file: How to Upload the Log File.

3

Which citra build are you using? (e.g: nightly 990)

1 Like
4

Nightly 1018 is being used

5

Try nightly-976, some mac users reported problems with the latest nightly builds, just download the citra-osx, extract to a folder and run citra-qt.

report if that works, so we can troubleshoot which build is causing the issue.

6

Thanks a ton. It works noww :smile:

7

Can you also test some other builds, it helps to find what is causing the issue.
for that, try nightly-977 and 978. that is because some users reported that 976 was the last one to work, other say its 977 and by testing 978 we can find if this build is also working.

8

I replied to the same error here: Citra wont open on MAC

At a glance it looks like the newer Citra builds are built on OS X 10.13 using a newer C++17 supporting libc++.

1 Like
9

Better submit an issue then i guess.