Memory Leak/Preformance Issue

[Titor]

Can confirm on an AMD HD 7900 series. Getting a lot of huge fps drops/crashes while teleporting. If I minimize the window and then bring it up again, the screen is completely black. Waiting a few minutes will usually cause it to resolve itself, but I have had to kill the process once or twice.

[Djarums]

Nothing I do helps get rid of the crashing.... it crashes in Windows 8, Windows 8.1, Windows 7. clean installs, upgrades, new drivers, old drivers.


Why is nothing being done to fix this leak? Why are we stil being charged for a game I can only play 60%. getting kicked due to crashes and being still "logged in"

This is pretty pathetic..

[Raist]

Nothing I do helps get rid of the crashing.... it crashes in Windows 8, Windows 8.1, Windows 7. clean installs, upgrades, new drivers, old drivers.


Why is nothing being done to fix this leak? Why are we stil being charged for a game I can only play 60%. getting kicked due to crashes and being still "logged in"

This is pretty pathetic..

It doesn't appear to be an issue with the game as much as an issue with specific hardware/software environments. More specifically, recent hardware/drivers from AMD. Older cards/drivers do not seem to suffer these issues. For example, I have no such issue with my older Sapphire 5870 Vapor-X nor my Asus GTX670MX--both running in Windows 8, and with older drivers.

Basically, this looks more like an issue with AMD's drivers not properly supporting the older DirectX9 crud that SE is using for this game. It is all run through emulation layers within the Windows API, and the newer cards and their drivers simply are not designed with as much focus and regression testing for the older DirectX API--they are more about DX10.1 or higher first and everything else second. Similar things used to happen all the time with XI as well and their DirectX 8.1/9.0c mixed bag of tricks (well, they probably still run into issues since it's still a hodge-podge design).

It's an underlying issue with proper vendor support for pre-DX10.1. The latest and greatest just typically are prone to having issues with these games because of their reliance on emulation for outdated API's (think Microsoft kicked DX9 to the curb in 2012 or something). We've had such issues for years now, and until they revamp clients to use true DX11 we will likely continue to see such issues.

[Mascis]

Has anyone tried this program called CleanMem?
I'm interested to know if this thing actually works...

[Nexxus]

I have crash in game and also Blue Screen, it's happend only on FFXIV.

As most of us, i use Windows 8.1 Pro x64
I was on Windows 7 before i changed to processor i7, SSD and 16Go Ram, and there was no problem at all with my Graphic Card (AMD Radeon HD 6900 series).
What i see, when i'm in the control panel, is that either my SSD or the processor sometimes get a high peak (FFXIV is at 1Go400~ Ram used).

I did try a lot of things like switch my graphic pilot to an older version or try the latest one. nothing change.

The Blue Screen appear often when i'm in a crowd area (usually when there's a lot of ppl that TP for an NM hunt), sometimes after i've hit the duty finder button (when the search found something and the pop up windows appear ?)....

[Squa11_Leonhart]

Has anyone tried this program called CleanMem?
I'm interested to know if this thing actually works...

such programs are snake oil, all they do is flush working set to the Page file, they do not free up any memory because they have no power over the applications memory management to do so.

[Nukocafe]

has anyone found a solution to this yet? I've had this issue for ages.
Crash in Mordhona, crash during large hunt mobs...sigh

[einwol]

The issue still persists i.e. if you hit the 1.45GB threshold the game dies.

LOD Streaming prevents the memory from accumulating indefinitely over time which triggered the issue. However, if a single area pushes the memory usage past that threshold, you will still crash. The zone area between Mordhona and Coerthas on the Revenant's Tool side seems to be a repeat offender to trigger the issue. Especially on high population servers where Revenant's Tool has a lot of players.

Note: I play at 5760x1200 so the issue occurs more often for me because I am constantly skirting the threshold of 1.45GB.

How can you tell you hit a threshold of 1.45gb. I'd like to monitor that on my system

[einwol]

With all of the posts on this thread, has SE acknowledged there is a problem officially? If not, Community Team, What are your thoughts?

When I talked to SE, the tech pointed me toward port forwarding saying that after updates they make changes to the ports they use. Every time I get a crash it is Event ID 1000 in event viewer which seems like a network error. I'm not sure because Microsoft did not have event ID 1000 defined. O.o

[Stoogie]

this issue has happened since 2.0 and causes the game to crash on teleport or sometimes standing around idle, it is happening due to a memory/texture coding issue between ATI hardware and the game itself, atm i get it about 2 times a day 5-10 hours playtime 13.9 drivers.

The LOD setting workaround as previously posted by Mapi should work, but i love my graphics definition :P


Operating System: Windows 7 Home Premium 64bit +HUD Machine(Green) Theme by Mr.Grim
Motherboard: Asus Maximus VI Hero
CPU: Intel Core i7 4770K @ 4.4ghz, 1.22v, HT on +Corsair Hydro H100i +2 Corsair Fans
Memory: 16gb(2x8gb) G.Skill Trident DDR3 @ 2400mhz 10-12-12-31-2N Timings, 1.65v
GPU: 2x Sapphire ATi Radeon HD 7950 Boost 3gb's in Crossfire @Stock 925/1250, 1.25v
Sound: SupremeFX Realtek ALC1150 Onboard
PSU: Corsair HX1050 +PSU Silicon Spacer
HDD: Total 11.25tb, Samsung 840 EVO 250gb SSD(Main), 2x Western Digital WD20EARS 2tb 5400RPM(Backups), 2x Seagate Barracuda ST3000DM001 3tb 7200RPM(Anime Drives), Seagate Barracuda ST1000DM003 1tb 7200RPM