Memory leak related to dashing?

[lolCindered]

The more I use the dash on the field, the more my framerate starts tank. Eventually animations completely break and get stuck at around 20 fps or so before I get a out of memory error, anybody else having this problem?

[TeKett]

the stutter could be caused by the faster loadtimes, it could spike the cpu and use more cpu for a shorter duration, it makes loding faster, but drops cpu power for all other operations causing frame drops and stretched audio. together with that the game tries to be minimal on the ram, constantly unloading data it issent using. mine always run around 300-450mb, rather then storing it and growing in size, so as soon as data becomes unused it unloads it even if the data will be used 5 seconds later, wich causes high cpu trafic wich causes micro stutter

but thats just my guess, other then ram load and unload stutter im running just fine on a i7 6700HQ 2.6ghz and GTX 970m and 16ram

as for the leak, im kinda uneducated in what it really means, but im guessing its when the program accidentally writes data outside of its given data range. wich could be caused by the program not allocating enought ram, wich could be caused by what iv said erlier about the game trying to be verry minimal on the ram usage.

[General Plastro]

Damn! So some folks are still having this issue?! I reported this issue not 2 days after the beta started.

Its not just dashing, jumping and attacking usually cause the issue too.

This problem was fixed for me when they upgraded the beta to 0.21.

If its the exact same problem i had in the initial version of the beta (0.15), alt tabbing in and out of the game fixed it for me.

And make sure your in fullscreen mode.

[Red]

Originally posted by きょすけ:

Originally posted by Rednavi:

It also added the redistributables so they get installed properly upon launching.

They were already added to me, in fact they tried to install themselves for the second time, lol.

Ah, then you're right. I forgot whether they were installed during my first launch so this was probably just the game installing them again.

I did notice some flickering in the water in the overworld map though. I don't recall that being there yesterday.

[きょすけ]

Originally posted by General Plastro:

Damn! So some folks are still having this issue?! I reported this issue not 2 days after the beta started.

Its not just dashing, jumping and attacking usually cause the issue too.

This problem was fixed for me when they upgraded the beta to 0.21.

If its the exact same problem i had in the initial version of the beta (0.15), alt tabbing in and out of the game fixed it for me.

And make sure your in fullscreen mode.

Did you experiment this issue on borderless mode even after said fix? Anyway no matter the setting, I still have stuttering :/

Originally posted by Rednavi:

Originally posted by きょすけ:

They were already added to me, in fact they tried to install themselves for the second time, lol.

Ah, then you're right. I forgot whether they were installed during my first launch so this was probably just the game installing them again.

I did notice some flickering in the water in the overworld map though. I don't recall that being there yesterday.

It happened to me too even at first launch of the game. It happens randomly and it seems to be fixed/caused by closing and booting the game again...

[RiO]

Originally posted by Zanameth:

Originally posted by きょすけ:

Great...so you reported it but still nothing :/

Memory leaks are really hard to deal with

Memory leaks are stupid easy to deal with, if you write your code with decent architecture in mind. Build on proper, vetted and well-tested code abstractions that don't have them and then don't perform unsafe pointer manipulations yourself.

When a video game has memory leaks its almost exclusively because a developer thought of something ... ' clever ' ...

And 9 out of 10 times said developer will be a veteran developer that is abusing their seniority to perpetuate coding practices from the 90s, because that's all they really know. (This is particularly a problem in asian software companies, it seems, which tend to still value seniority over actual technical expertise.)

[Zanameth]

Originally posted by RiO:

Originally posted by Zanameth:

Memory leaks are really hard to deal with

Memory leaks are stupid easy to deal with, if you write your code with decent architecture in mind. Build on proper, vetted and well-tested code abstractions that don't have them and then don't perform unsafe pointer manipulations yourself.

That's a big "if", unfortunately. Peer review for all commits helps a lot in those cases, though I'm not sure how standard these are in the game industry.

[RiO]

Originally posted by Zanameth:

Originally posted by RiO:

Memory leaks are stupid easy to deal with, if you write your code with decent architecture in mind. Build on proper, vetted and well-tested code abstractions that don't have them and then don't perform unsafe pointer manipulations yourself.

That's a big "if", unfortunately. Peer review for all commits helps a lot in those cases, though I'm not sure how standard these are in the game industry.

The video game industry still largely abuses play-testers to locate functional bugs, instead of relying on automated unit testing and integration testing for that. I highly doubt peer reviews rank high on the list of "in use".

[davidb11]

I can point out this bug does not bother me, so it must be a memory leak that requires specific hardware to find it.

I've used Dash about 20 times in a row, and I would imagine that would cause the bug to appear.
Maybe the recent patches have fixed it?

[DarkScythe]

Originally posted by General Plastro:

This problem was fixed for me when they upgraded the beta to 0.21.

According to my notes, it was never fully 'fixed' even in v0.21. I reported a memory leak several times as well, and it was improved in v0.20 based on my testing, but I stressed to IFI pior to release that it was still in an unacceptable state.

That said, remember that IFI aren't really the developers of the game. I'm not sure if they handled the entire porting process on their own, or if CH / IF (not International) did it and then handed it to IFI to localize. If this is the case, IFI would likely have to bug CH / IF to make the necessary changes to improve memory usage and would thus be at their mercy.

A reliable work-around, as with any memory-leaking application, is to simply restart the game every now and then. I can get annoying, but at least you can easily save the game between dungeons. In my testing, it didn't get crazy until I had played about 3-4 hours or more.