mac m1, performance issues and error with updating and login

i have a few issues i would like to report;

1. entering a town instantly tanks my fps to 5-10 because of all the damn mtx people wear. sometimes it takes me longer to finish everything i have to do in town than it takes to clear a map. this is really bad :(

2. when using the RF skill, when you walk over corpses or grass or something like that, there is an golden disintegrating-effect shown making these objects burn. this effect alone costs me around 10-20fps and occurs during regular gameplay all the time. please is there any way to disable it?

3. when patching via steam, the update cant be installed properly with an error "cant wrtite do hdd" shown. after rebooting the system it works

4. you have added a layer of rng to the client login and i am not a huge fan of it. sometimes i have to repopen the client 10+ times before a login will succseed and i can play the game. a way to know that the login wont work is in the char-selection screen all the models will be very low-poly and washed out. when they are shown normaly, login will always work.

5. overall, the game seems to be poorly optimized on mac. i have much better performance on my steamdeck. which is kinda very odd imo


thanks and all the best
Last bumped on Aug 21, 2024, 5:22:53 PM
I can't comment on 1,2 & 5 but 3 & 4 are the current banes of my existence.
I have encountered issues 1, 3, and 5. Possibly issue 2 as well (I play RF to reduce flashes, effects, and some particles), but I haven't pinpointed the cause of the FPS drop during fights. I understand your frustration with it..
I have experienced all five too!

#3 I resolved by granting 'Full Disc Access' permission to Steam.

#4 Rebooting, re-installing, re-trying. I have not found anything to be consistently letting log in and play. The low poly / washed out loading is dead giveaway, but I am also getting "instant game closed". Both of these events are followed by a crash report window.

#5 I have to play windowed, but want to play full screen. The new scaling system seems like a step in the right direction at least.
You're able to get past character selection? I've tried about 50-60 times over 4 days, and it either crashes or "failed to connect to instance" followed by "unable to connect to login server".
You have to re-open the game for each log in attempt. It seems utterly random if your attempt succeeds or not.

After my last reply I started continuously retrying and had lost hope after the first 10 attempts, but was hoping to make the repeated crashes stand out in GGGs logs :-) Out of nowhere and with no additional steps to what had been failing for maybe 10-15 minutes the game loaded me in...
after 50 logins and "failed to connect to instance" after clicking my char, i gave up.

m3pro, 36gig ram


oh, i managed a crash:

"
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: PathOfExileClient [93144]
Path: /Users/USER/Library/Application Support/Steam/*/PathOfExileClient.app/Contents/MacOS/PathOfExileClient
Identifier: com.GGG.PathOfExile
Version: 1.0 (???)
Code Type: X86-64 (Translated)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2024-08-01 10:30:36.9258 +0200
OS Version: macOS 14.5 (23F79)
Report Version: 12
Anonymous UUID: B56E8DCC-7F2B-FDC2-4497-7DE06F017E17

Sleep/Wake UUID: 9E27A565-F995-4FA4-BD08-4A0A61CCEFF7

Time Awake Since Boot: 490000 seconds
Time Since Wake: 84 seconds

System Integrity Protection: enabled

Notes:
PC register does not match crashing frame (0x0 vs 0x7FF899C56A78)

Crashed Thread: 19

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: PathOfExileClient [93144]

Application Specific Information:
abort() called


Error Formulating Crash Report:
PC register does not match crashing frame (0x0 vs 0x7FF899C56A78)
Last edited by danielray on Aug 1, 2024, 4:32:03 AM
There might be higher success if you:

- Launch Game
- Wait 15 seconds
- Login
- Press play as fast as you can


---------
Updated:

Last 4 times I had to login and doing the steps above I get one failure and then on the next try I am logged in.
Last edited by codereaper on Aug 2, 2024, 1:29:15 PM
I somehow avoided the Mac client login issue for a few days, but it's back again.

Edit: if I spam Enter key to Login and Play as fast as possible, I can make it past Play, then client crashes instantly, or (rarely) I get "Failed to connect to instance."

A few stack traces for just the crashed threads, several of which indicate a failure inside malloc():

"
Thread 17 Crashed:
0 ??? 0x7ff8a26d2a84 ???
1 libsystem_kernel.dylib 0x7ff81237eb52 __pthread_kill + 10
2 libsystem_pthread.dylib 0x7ff8123b8f85 pthread_kill + 262
3 libsystem_c.dylib 0x7ff8122d9b19 abort + 126
4 libsystem_malloc.dylib 0x7ff8121d8e91 malloc_vreport + 857
5 libsystem_malloc.dylib 0x7ff8121dc96b malloc_report + 151
6 PathOfExileClient 0x103707f61 0x102096000 + 23535457
7 PathOfExileClient 0x1039f06d8 0x102096000 + 26584792
8 PathOfExileClient 0x1039efb9b 0x102096000 + 26581915
9 PathOfExileClient 0x105d419f9 0x102096000 + 63617529
10 PathOfExileClient 0x10260fd27 0x102096000 + 5741863
11 PathOfExileClient 0x1037087a4 0x102096000 + 23537572
12 PathOfExileClient 0x1042767e9 0x102096000 + 35522537
13 PathOfExileClient 0x10427b4ba 0x102096000 + 35542202
14 PathOfExileClient 0x10427b2f0 0x102096000 + 35541744
15 libsystem_pthread.dylib 0x7ff8123b9253 _pthread_start + 99
16 libsystem_pthread.dylib 0x7ff8123b4bef thread_start + 15


"
Thread 17 Crashed:
0 ??? 0x7ff8a26d2a84 ???
1 libsystem_kernel.dylib 0x7ff81237eb52 __pthread_kill + 10
2 libsystem_pthread.dylib 0x7ff8123b8f85 pthread_kill + 262
3 libsystem_c.dylib 0x7ff8122d9b19 abort + 126
4 libsystem_malloc.dylib 0x7ff8121d8e91 malloc_vreport + 857
5 libsystem_malloc.dylib 0x7ff8122002d7 malloc_zone_error + 183
6 libc++.1.dylib 0x7ff8122f8d3b std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t>>::__grow_by(unsigned long, unsigned long, unsigned long, unsigned long, unsigned long, unsigned long) + 251
7 libc++.1.dylib 0x7ff8122f8dca std::__1::basic_string<wchar_t, std::__1::char_traits<wchar_t>, std::__1::allocator<wchar_t>>::push_back(wchar_t) + 108
8 PathOfExileClient 0x1013fa4b1 0x100f57000 + 4863153
9 libc++.1.dylib 0x7ff812305482 std::__1::basic_streambuf<wchar_t, std::__1::char_traits<wchar_t>>::xsputn(wchar_t const*, long) + 122
10 PathOfExileClient 0x1013fa92a 0x100f57000 + 4864298
11 PathOfExileClient 0x1013fa675 0x100f57000 + 4863605
12 PathOfExileClient 0x1028b1504 0x100f57000 + 26584324
13 PathOfExileClient 0x1028b0b9b 0x100f57000 + 26581915
14 PathOfExileClient 0x104c029f9 0x100f57000 + 63617529
15 PathOfExileClient 0x1014d0d27 0x100f57000 + 5741863
16 PathOfExileClient 0x1025c97a4 0x100f57000 + 23537572
17 PathOfExileClient 0x1031377e9 0x100f57000 + 35522537
18 PathOfExileClient 0x10313c4ba 0x100f57000 + 35542202
19 PathOfExileClient 0x10313c2f0 0x100f57000 + 35541744
20 libsystem_pthread.dylib 0x7ff8123b9253 _pthread_start + 99
21 libsystem_pthread.dylib 0x7ff8123b4bef thread_start + 15


"
Thread 16 Crashed:
0 ??? 0x7ff8a26d2a84 ???
1 libsystem_kernel.dylib 0x7ff81237eb52 __pthread_kill + 10
2 libsystem_pthread.dylib 0x7ff8123b8f85 pthread_kill + 262
3 libsystem_c.dylib 0x7ff8122d9b19 abort + 126
4 libc++abi.dylib 0x7ff812370163 abort_message + 258
5 libc++abi.dylib 0x7ff8123610ce demangling_terminate_handler() + 266
6 libobjc.A.dylib 0x7ff81200110b _objc_terminate() + 104
7 libc++abi.dylib 0x7ff81236f53b std::__terminate(void (*)()) + 6
8 libc++abi.dylib 0x7ff8123723b4 __cxa_rethrow + 100
9 PathOfExileClient 0x1025fa91d 0x10041a000 + 35522845
10 PathOfExileClient 0x1025ff4ba 0x10041a000 + 35542202
11 PathOfExileClient 0x1025ff2f0 0x10041a000 + 35541744
12 libsystem_pthread.dylib 0x7ff8123b9253 _pthread_start + 99
13 libsystem_pthread.dylib 0x7ff8123b4bef thread_start + 15


"
Thread 20 Crashed:
0 ??? 0x7ff8a26d2a84 ???
1 libsystem_kernel.dylib 0x7ff81237eb52 __pthread_kill + 10
2 libsystem_pthread.dylib 0x7ff8123b8f85 pthread_kill + 262
3 libsystem_c.dylib 0x7ff8122d9b19 abort + 126
4 libsystem_malloc.dylib 0x7ff8121d8e91 malloc_vreport + 857
5 libsystem_malloc.dylib 0x7ff8122002d7 malloc_zone_error + 183
6 libsystem_malloc.dylib 0x7ff8121ef914 nanov2_guard_corruption_detected + 34
7 libsystem_malloc.dylib 0x7ff8121ef8de nanov2_allocate_outlined + 407
8 libsystem_malloc.dylib 0x7ff8121cbfba nanov2_malloc + 543
9 libsystem_malloc.dylib 0x7ff8121fa875 _malloc_zone_memalign + 329
10 libsystem_malloc.dylib 0x7ff8121fae1c _posix_memalign + 44
11 PathOfExileClient 0x104b3e3e9 0x102953000 + 35566569
12 PathOfExileClient 0x102c55581 0x102953000 + 3155329
13 PathOfExileClient 0x102b6c92e 0x102953000 + 2201902
14 PathOfExileClient 0x102a1f18d 0x102953000 + 835981
15 PathOfExileClient 0x102a974c2 0x102953000 + 1328322
16 PathOfExileClient 0x102a75dd8 mvk::SPIRVToMSLConverter::convert(mvk::SPIRVToMSLConversionConfiguration&, mvk::SPIRVToMSLConversionResult&, bool, bool, bool) + 440
17 PathOfExileClient 0x102a5c653 0x102953000 + 1087059
18 PathOfExileClient 0x102a5c30b 0x102953000 + 1086219
19 PathOfExileClient 0x102a5cf9f 0x102953000 + 1089439
20 PathOfExileClient 0x102a1bda9 0x102953000 + 822697
21 PathOfExileClient 0x102a1b3d4 0x102953000 + 820180
22 PathOfExileClient 0x1029fbf08 0x102953000 + 691976
23 PathOfExileClient 0x102979286 vkCreateComputePipelines + 86
24 PathOfExileClient 0x104bacc85 0x102953000 + 36019333
25 PathOfExileClient 0x104baca25 0x102953000 + 36018725
26 PathOfExileClient 0x104bceb6b 0x102953000 + 36158315
27 PathOfExileClient 0x104e6e4e1 0x102953000 + 38909153
28 PathOfExileClient 0x104e53b12 0x102953000 + 38800146
29 PathOfExileClient 0x104e4c7ce 0x102953000 + 38770638
30 PathOfExileClient 0x104e65fce 0x102953000 + 38875086
31 PathOfExileClient 0x104e6629a 0x102953000 + 38875802
32 PathOfExileClient 0x104b337e9 0x102953000 + 35522537
33 PathOfExileClient 0x104b384ba 0x102953000 + 35542202
34 PathOfExileClient 0x104b382f0 0x102953000 + 35541744
35 libsystem_pthread.dylib 0x7ff8123b9253 _pthread_start + 99
36 libsystem_pthread.dylib 0x7ff8123b4bef thread_start + 15
Last edited by Tunzophun on Aug 3, 2024, 1:21:49 PM
Another symptom: Directly after client restart and before login, I selected a different gateway. All the gateways were reporting typical pings in the list. The login failed with "> Connecting to login server > Unable to connect to login server." After that, the list of gateways showed all the pings as "?".

It's probably just a side effect of some random memory corruption, but it is fairly repeatable, and I thought it was interesting.

Report Forum Post

Report Account:

Report Type

Additional Info