*** Patch 1.3.4 fails to fix game-breaking memory leak / FPS lag in PvP ***

onlinegamer1

Please hotfix this memory leak asap. We can't wait another week for a fix.

dcincali

But

Barrier: Fixed an issue where the damage shield could be stacked multiple times

Was "fixed". Which wasn't an issue anywhere ever...

Komma

I haven't had any more lag than normal but the memory leak needs fixin!

Delorion

agree we need a fix for this asap its just bad that eso crash at least once a hour with exceeding 3,7gbyte memory... many ppl are plagued by it in cyrodiil

twev

Working as intended.

The game engine itself is a stealth enemy.

Devlinne

ZOS! lets give u the benefit of the doubt. Perhaps...SOMEHOW...u didn't know or realise that since patch 1.33, your game has been crashing ALOT more than usual. And pvp lag is thrown back to a bad state, whereas we enjoyed it REAL GOOD for about 2-3 weeks before patch 1.33

Please do whatever is necessary.
It's real nice you fixed this and that. THANKS.

BUT....game crashing is a serious issue. It deserves some special IMMIDIATE attention no?

Extend the maintainance or something if u have to. But fix it.

dean_steusloffub17_ESO

The memory leak issue is horrendous, and it's even worse if you leave the launcher open. C'mon guys, deal with the real issues, not minimalist garbage that no one even realized was broken.

Komma

They didn't take it seriously so they haven't got a fix for it yet. Extending the maintenance wont help anything.

Xsorus

dcincali wrote: »

But

Barrier: Fixed an issue where the damage shield could be stacked multiple times

Was "fixed". Which wasn't an issue anywhere ever...

Actually it was a fairly major pvp issue

Iorail

And the OP knows this because he can magically log in on a server that's still down...... Wait for the game to come back up before making any claims....

Komma

Hopefully some of the broken things they fixed are what caused the memory leak. Fingers crossed otherwise it will be at least another week or maybe longer until they realize it is most if not all people that have it.

dcincali

xsorusb14_ESO wrote: »

dcincali wrote: »

But

Barrier: Fixed an issue where the damage shield could be stacked multiple times

Was "fixed". Which wasn't an issue anywhere ever...

Actually it was a fairly major pvp issue

Reading in the forums since launch, I have never read anything in relation to stacking barriers being an issue. Most barriers are blown off with the first pour of oil over the breach. So if your group isn't using oil or doesn't have the dps to burn off a barrier, there is more of an issue then just stacking them.

Top 3 issues in PVP currently:

Disconnects

Impulse/blob groups

Bat swarms

UPrime

OP is right! They should shut down the rest of the company while the team that's already investigating the memory leak/FPS continues to do so.

onlinegamer1

Iorail wrote: »

And the OP knows this because he can magically log in on a server that's still down...... Wait for the game to come back up before making any claims....

I know this because:
1. I can read patch notes, unlike you, apparently.
2. I already downloaded the patch, and it was small (would HAVE to be bigger if there was a new Client)
3. Its still on the known issues list, which you also apparently can't read.

I believe the saying on the streets is... "pwned".

Circuitous

onlinegamer1 wrote: »

I believe the saying on the streets is... "pwned".

Yeah, no, it's not.

Sallington

Yeah ZOS! Delete the memory leak line of code! What's taking so long, just delete it?!?!

Xsorus

dcincali wrote: »

xsorusb14_ESO wrote: »

dcincali wrote: »

But

Barrier: Fixed an issue where the damage shield could be stacked multiple times

Was "fixed". Which wasn't an issue anywhere ever...

Actually it was a fairly major pvp issue

Reading in the forums since launch, I have never read anything in relation to stacking barriers being an issue. Most barriers are blown off with the first pour of oil over the breach. So if your group isn't using oil or doesn't have the dps to burn off a barrier, there is more of an issue then just stacking them.

Top 3 issues in PVP currently:

Disconnects

Impulse/blob groups

Bat swarms

I'm just going to go ahead and bold this right here.. and let ya think on it for a second.

Karikin

agreed, I don't care if it has to be down for the next 8 hours. Get those memory leaks fixed for both Mac and PC clients! Hell! even PvEers are getting hit by this memory leak!

Cyberdown

So you guys are all 100% sure its a super easy fix that should have been in this patch then?

Maybe they should change a value in the code from "memoryleak:yes" to "memoryleak:no"

also im always curious with memory leak thread complaints...as it seems to be the cover all issue to any lag related issue in game...feel free to post a screenie of all your task managers showing an actual memory leak on the ESO client.

Iorail

onlinegamer1 wrote: »

Iorail wrote: »

And the OP knows this because he can magically log in on a server that's still down...... Wait for the game to come back up before making any claims....

I know this because:
1. I can read patch notes, unlike you, apparently.
2. I already downloaded the patch, and it was small (would HAVE to be bigger if there was a new Client)
3. Its still on the known issues list, which you also apparently can't read.

I believe the saying on the streets is... "pwned".

Hardly

The Elder Scrolls Online v1.3.4 is an incremental patch that features updates to gameplay,

If you have any idea how ZOS do their patch notes, you will know that they never put concrete information in their patch notes, that the sentence above is as much information as you are going to get until you log in. But in a good note, now you know what to do the next time so no foot in mouth combo occurs anymore.

c0rp

Pretty dissapointed that this issue is going to be present for at least another week. Pretty much means I wont be playing PvP at all...which is the only thing keeping me subbed to eso.

onlinegamer1

Iorail wrote: »

onlinegamer1 wrote: »

Iorail wrote: »

And the OP knows this because he can magically log in on a server that's still down...... Wait for the game to come back up before making any claims....

I know this because:
1. I can read patch notes, unlike you, apparently.
2. I already downloaded the patch, and it was small (would HAVE to be bigger if there was a new Client)
3. Its still on the known issues list, which you also apparently can't read.

I believe the saying on the streets is... "pwned".

Hardly

The Elder Scrolls Online v1.3.4 is an incremental patch that features updates to gameplay,

If you have any idea how ZOS do their patch notes, you will know that they never put concrete information in their patch notes, that the sentence above is as much information as you are going to get until you log in. But in a good note, now you know what to do the next time so no foot in mouth combo occurs anymore.

4. The ZoS devs already said so.

ZOS_GinaBruno wrote: »

Delorion wrote: »

Nothing about the Memory Leak and Crashing in Cyrodiil that happens to a lot of players very frequently since 1.3.3 ? sad hard crashes should be number 1 priority. when you are in a big raid always 2-3 ppl seems to crash i for myself crash all 60-90 minutes with eso.exe using 3,7 gbyte memory...

We are actively looking into this issue, and will give everyone an update as soon as we have one. It will likely be in the Known Issues thread first.

Tabbycat wrote: »

@ZOS_GinaBruno, I have a question for clarification.

You are now required to defeat all Trials bosses for your score to be recorded on the Trials Leaderboards.

Are the leaderboards reset? If someone was getting extremely low times for not killing all the trials bosses, won't that make it impossible to beat that time after the patch?

We're checking on this now.

Want to keep replying and getting WTFPWNED?

butterfly442

dcincali wrote: »

xsorusb14_ESO wrote: »

dcincali wrote: »

But

Barrier: Fixed an issue where the damage shield could be stacked multiple times

Was "fixed". Which wasn't an issue anywhere ever...

Actually it was a fairly major pvp issue

Reading in the forums since launch, I have never read anything in relation to stacking barriers being an issue. Most barriers are blown off with the first pour of oil over the breach. So if your group isn't using oil or doesn't have the dps to burn off a barrier, there is more of an issue then just stacking them.

Top 3 issues in PVP currently:

Disconnects

Impulse/blob groups

Bat swarms

You obviously didn't realize "how" they were stacking, and "what" was stacking.

It NEEDED fixed.

Komma

Cyberdown wrote: »

So you guys are all 100% sure its a super easy fix that should have been in this patch then?

Maybe they should change a value in the code from "memoryleak:yes" to "memoryleak:no"

also im always curious with memory leak thread complaints...as it seems to be the cover all issue to any lag related issue in game...feel free to post a screenie of all your task managers showing an actual memory leak on the ESO client.

The op said lag but this isn't a lag issue. Over time your memory builds up for eso . eventually your client will shut down. The more intense the battles the faster it fills up which is why most pve folks don't even notice it which is why zen is blowing it off.

DuelWieldingCheesyPoofs

Lol

Homm

Go to hell ZOS if you won't fix this in 1.3.4. We don't want useless smal fixes, we want this gamebreaking serious bug fixed!

dcincali

butterfly442 wrote: »

dcincali wrote: »

xsorusb14_ESO wrote: »

dcincali wrote: »

But

Barrier: Fixed an issue where the damage shield could be stacked multiple times

Was "fixed". Which wasn't an issue anywhere ever...

Actually it was a fairly major pvp issue

Reading in the forums since launch, I have never read anything in relation to stacking barriers being an issue. Most barriers are blown off with the first pour of oil over the breach. So if your group isn't using oil or doesn't have the dps to burn off a barrier, there is more of an issue then just stacking them.

Top 3 issues in PVP currently:

Disconnects

Impulse/blob groups

Bat swarms

You obviously didn't realize "how" they were stacking, and "what" was stacking.

It NEEDED fixed.

My group knew barrier stacked twice and only used it to rush a breach or the first encounter with a large zerg. It only hits 16 people so if you run with 24 you have 8 with nothing assuming they are out of range of the cast. If you are talking about warhorn then barrier or other combos.. Don't be mad you got out played.

xsorusb14_ESO wrote: »

dcincali wrote: »

xsorusb14_ESO wrote: »

dcincali wrote: »

But

Barrier: Fixed an issue where the damage shield could be stacked multiple times

Was "fixed". Which wasn't an issue anywhere ever...

Actually it was a fairly major pvp issue

Reading in the forums since launch, I have never read anything in relation to stacking barriers being an issue. Most barriers are blown off with the first pour of oil over the breach. So if your group isn't using oil or doesn't have the dps to burn off a barrier, there is more of an issue then just stacking them.

Top 3 issues in PVP currently:

Disconnects

Impulse/blob groups

Bat swarms

I'm just going to go ahead and bold this right here.. and let ya think on it for a second.

Yea, sorry that my 12 man group using 2 barriers could wipe out 40+ stacking much more... Nerf it please..

IKilled007

UPrime wrote: »

OP is right! They should shut down the rest of the company while the team that's already investigating the memory leak/FPS continues to do so.

No false dichotomy there...

Obscure

Memory leaks and such aren't that important at this stage in ESO's development. Once ZOS has the build feature complete, they'll take care of the bugs their tester group has identified for them afterwards. The PC and MAC test platforms for ESO have very dedicated testers to find and catalog these bugs for them, so dedicated in fact we're even testing the business model by purchasing the product giving them a subscription fee. Based on the figures they have reliable feedback on even that model to determine what changes are necessary for the game at launch.

These things will certainly be taken care of prior to ESO's yet to be announced release date. Rest assured they'll have it fixed up and running smoothly for launch, so make sure you have your XBone or your PS4 ready to go! Soon the fruits of all our rigorous testing will be realized in the launch state build of ESO. We're almost there fellow testers!

#paidbeta #unpaidqualitycontrol

LunaRae

Haven't been experiencing nasty lag, per se - but definitely crashing a LOT more than usual in Cyrodiil. Everyone in my group crashes at least 4-5 times in a 4-6 hour session, with no notable event. Can happen at anytime for no apparent reason.

WebBull

LunaRae wrote: »

Haven't been experiencing nasty lag, per se - but definitely crashing a LOT more than usual in Cyrodiil. Everyone in my group crashes at least 4-5 times in a 4-6 hour session, with no notable event. Can happen at anytime for no apparent reason.

It happens for the reason listed in the title of the post, memory leak. As soon as you get around 3.5gb mem .....crash incoming. You can monitor and avoid it by logging out and back in around 3gb mem.

This needs to be Priority #1 fix.