Mac Client has memory leak trying to register the registration code

The new 64 bit Mac client just sits there and eats up application space until it reaches 260 GB and the Mac OS tells me I'm out of application space and need to kill the process.

I have a PS4 and Windows Client that both work great. I run the Mac client on a new Mac with all OS and apps up to date. Only have FFXIV installed and one other program Ableton Live.

The Mac client lets me log in. Pick a service account, then when I click next after picking the service account it just sits there eating up application space until I have to kill the process.

I've verified ports are open (the fact I can play on ps4 and windows demonstrates that this isn't connectivity).

No other applications are running.

MacOS Mojave 10.14.5 - 32 Gigs of RAM Radeon ProVega 20 4 GB 2.9 GHz Intel Core i9 6 cores.


When submitting a bug report, please use the below template and thoroughly fill out the necessary information.

NOTE: I can't even get into game so I'll ignore that info.

Date & Time: Any date or time after release of Shadowbringers and new Mac 64 bit client
Frequency: Always
World name: Famfrit
Character name: Zana Admi
Retainer name:
NPC name:
Monster name:
Class/Level:
Party or solo:


In-game time:
Area and coordinates:
Housing:
Steps:
1.
2.
3.
*Add more steps if necessary

Connection Specs
- Type of internet connection/provider:
- Modem maker/model number:

■ PC Specs

To obtain the system information, open the FFXIV launcher and select Config → System Information → Display.

-=-=-=-=- System Information -=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


Laptop Model Name:
Laptop Model Number:

Gamepad Manufacturer:
Gamepad Model Name:
Gamepad Part Number:

Browser Information
- Name and version of the browser currently in-use:
- Internet Explorer Version:

------------------------------------------------------

■ PS4 Specs

Model Number of the PlayStation®4 You Are Using
- Model Number:

Model Number of the PlayStation®Vita You Are Using
- Model Number:

Information About the Peripherals You Are Using
-Type:
-Maker:
-Model Number:

Same here... Did you find a solution?
I already sent a message to Square Enix but they did not reply me by far.

Hi everyone
I had this issue as well, I fixed it by registering the license key on mogstation using a browser. After that, you should be able to log in and play without the memory leak issue. If it still doesn't work after registering your mac key on mogstation, try uninstalling the game (including removing any FFXIV folders/files in your mac's Application Support Library folder) and then reinstalling it. I reinstalled before playing as I live in Europe and accidentally downloaded the NA client, I don't think that was the cause of the memory leak, but it's better to be on the safe side I guess. Hope this helps! :)

Quote:

---

Originally Posted by cupofcoffee

Hi everyone
I had this issue as well, I fixed it by registering the license key on mogstation using a browser. After that, you should be able to log in and play without the memory leak issue. If it still doesn't work after registering your mac key on mogstation, try uninstalling the game (including removing any FFXIV folders/files in your mac's Application Support Library folder) and then reinstalling it. I reinstalled before playing as I live in Europe and accidentally downloaded the NA client, I don't think that was the cause of the memory leak, but it's better to be on the safe side I guess. Hope this helps! :)

---

I have just tested today, and at least in my MacBook Air, this was the only method that worked. Thank you for sharing this information.

Good afternoon and thank you for posting in the Final Fantasy XIV Technical Support Forums.

How long have you been experiencing this issue? Could you try uninstalling and reinstalling the application?


Thank you for visiting the Final Fantasy XIV Technical Support Forums!

Also experiencing the same issue on a brand new 2019 MacBook Pro.... completely unacceptable that the solution is to go to mogstation but that's what fixed it ! thanks guys for figuring it out.