I think I found what is causing the fps issues

It's a memory leak, I am 80% positive that it's a memory leak causing the fps issues

Comments

  • not saying i don't believe you but what evidence do you have for this?

  • @DragonMasterDarren said:

    not saying i don't believe you but what evidence do you have for this?

    Memory leaks usually happen in the code and well, I don't have access to the source code so I cannot 100% say that it's causing it, hence why I said 80% sure


    But the stability of this update is incredibly bad, and Mem leaks can cause stability issues

  • Yes but memory leaks usually cause slowdowns over time. IE: The longer you play, the worse the slowdown gets, as code is writing to/from the memory in a way that starts overloading the CPU or GPU.

  • I have a few questions.

    1. What is a memory leak and what causes it?

    And

    2. How does something like the memory of the game effect something like FPS? They don't seem to be related to each other.

  • All well and good, but the where is more important.

  • @dspaceman20 said:

    I have a few questions.

    1. What is a memory leak and what causes it?

    And

    2. How does something like the memory of the game effect something like FPS? They don't seem to be related to each other.

    In computer science, a memory leak is a type of resource leak that occurs when a computer program incorrectly manages memory allocations in a way that memory which is no longer needed is not released. A memory leak may also happen when an object is stored in memory but cannot be accessed by the running code. A memory leak has symptoms similar to a number of other problems and generally can only be diagnosed by a programmer with access to the programs' source code.

    A space leak occurs when a computer program uses more memory than necessary. In contrast to memory leaks, where the leaked memory is never released, the memory consumed by a space leak is released, but later than expected.

    Because they can exhaust available system memory as an application runs, memory leaks are often the cause of or a contributing factor to software aging.

    A memory leak reduces the performance of the computer by reducing the amount of available memory. Eventually, in the worst case, too much of the available memory may become allocated and all or part of the system or device stops working correctly, the application fails, or the system slows down vastly due to thrashing.

  • @Power_Guy said:

    https://forum.deadbydaylight.com/en/discussion/comment/2331867#Comment_2331867

    In computer science, a memory leak is a type of resource leak that occurs when a computer program incorrectly manages memory allocations in a way that memory which is no longer needed is not released. A memory leak may also happen when an object is stored in memory but cannot be accessed by the running code. A memory leak has symptoms similar to a number of other problems and generally can only be diagnosed by a programmer with access to the programs' source code.

    A space leak occurs when a computer program uses more memory than necessary. In contrast to memory leaks, where the leaked memory is never released, the memory consumed by a space leak is released, but later than expected.

    Because they can exhaust available system memory as an application runs, memory leaks are often the cause of or a contributing factor to software aging.

    A memory leak reduces the performance of the computer by reducing the amount of available memory. Eventually, in the worst case, too much of the available memory may become allocated and all or part of the system or device stops working correctly, the application fails, or the system slows down vastly due to thrashing.

    This is really interesting. So how would you fix a memory leak.

  • @Power_Guy said:

    https://forum.deadbydaylight.com/en/discussion/comment/2331867#Comment_2331867

    In computer science, a memory leak is a type of resource leak that occurs when a computer program incorrectly manages memory allocations in a way that memory which is no longer needed is not released. A memory leak may also happen when an object is stored in memory but cannot be accessed by the running code. A memory leak has symptoms similar to a number of other problems and generally can only be diagnosed by a programmer with access to the programs' source code.

    A space leak occurs when a computer program uses more memory than necessary. In contrast to memory leaks, where the leaked memory is never released, the memory consumed by a space leak is released, but later than expected.

    Because they can exhaust available system memory as an application runs, memory leaks are often the cause of or a contributing factor to software aging.

    A memory leak reduces the performance of the computer by reducing the amount of available memory. Eventually, in the worst case, too much of the available memory may become allocated and all or part of the system or device stops working correctly, the application fails, or the system slows down vastly due to thrashing.

    I wish I took a picture but for some reason Xbox removes error messages after a set amount of time, but I got an error stating I was "out of video memory" I believe before it booted me out of Dbd

  • @dspaceman20 said:

    https://forum.deadbydaylight.com/en/discussion/comment/2331871#Comment_2331871

    This is really interesting. So how would you fix a memory leak.

    You need to figure out if it's just not clearing the memory as needed, or if something is writing to memory and then not being unloaded (perhaps loading pallets in one map, then not clearing them before loading a new map.)

    It really boils down to WHAT and WHERE, and the larger the game, the harder it can be to find. I've had a friend write Python 3 for me with small errors for me to find, and even when it's something as simple as a letter-replacement program (IE: You press 'A' and then enter, and it returns 'Q'), the bugs or typos can be hard to find, nested in the code.

    Trying to find a memory leak in a 3D game, which has to call objects such as rocks, trees, crows, pallets, walls, etc. AND their hitboxes, plus characters & killers, and their animations...I don't envy BHVR trying to work through this!


    @Hoodied said:

    https://forum.deadbydaylight.com/en/discussion/comment/2331871#Comment_2331871

    I wish I took a picture but for some reason Xbox removes error messages after a set amount of time, but I got an error stating I was "out of video memory" I believe before it booted me out of Dbd

    That does make it sound like a memory leak.

  • DbD does suffer of memory leak since ever

  • I personally think it's a low ram issue. Since my old computer only had 8gb ram, and this game would run horribly. I would suffer from stuttering based on the map such as lerrys the middle room. Basically all the issue old console gens suffer from. And thankfully I bought another 8gb ram stick on my old pc, and what do you know my those issues stopped. Since old console gens have 8gb as well.

  • @Power_Guy said:

    https://forum.deadbydaylight.com/en/discussion/comment/2331884#Comment_2331884

    You need to figure out if it's just not clearing the memory as needed, or if something is writing to memory and then not being unloaded (perhaps loading pallets in one map, then not clearing them before loading a new map.)

    It really boils down to WHAT and WHERE, and the larger the game, the harder it can be to find. I've had a friend write Python 3 for me with small errors for me to find, and even when it's something as simple as a letter-replacement program (IE: You press 'A' and then enter, and it returns 'Q'), the bugs or typos can be hard to find, nested in the code.

    Trying to find a memory leak in a 3D game, which has to call objects such as rocks, trees, crows, pallets, walls, etc. AND their hitboxes, plus characters & killers, and their animations...I don't envy BHVR trying to work through this!

    https://forum.deadbydaylight.com/en/discussion/comment/2331887#Comment_2331887

    That does make it sound like a memory leak.

    I understand now. Thanks for explaining it

  • @Power_Guy said:

    https://forum.deadbydaylight.com/en/discussion/comment/2331867#Comment_2331867

    In computer science, a memory leak is a type of resource leak that occurs when a computer program incorrectly manages memory allocations in a way that memory which is no longer needed is not released. A memory leak may also happen when an object is stored in memory but cannot be accessed by the running code. A memory leak has symptoms similar to a number of other problems and generally can only be diagnosed by a programmer with access to the programs' source code.

    A space leak occurs when a computer program uses more memory than necessary. In contrast to memory leaks, where the leaked memory is never released, the memory consumed by a space leak is released, but later than expected.

    Because they can exhaust available system memory as an application runs, memory leaks are often the cause of or a contributing factor to software aging.

    A memory leak reduces the performance of the computer by reducing the amount of available memory. Eventually, in the worst case, too much of the available memory may become allocated and all or part of the system or device stops working correctly, the application fails, or the system slows down vastly due to thrashing.

    Fascinating!

  • @Power_Guy said:

    https://forum.deadbydaylight.com/en/discussion/comment/2331884#Comment_2331884

    You need to figure out if it's just not clearing the memory as needed, or if something is writing to memory and then not being unloaded (perhaps loading pallets in one map, then not clearing them before loading a new map.)

    It really boils down to WHAT and WHERE, and the larger the game, the harder it can be to find. I've had a friend write Python 3 for me with small errors for me to find, and even when it's something as simple as a letter-replacement program (IE: You press 'A' and then enter, and it returns 'Q'), the bugs or typos can be hard to find, nested in the code.

    Trying to find a memory leak in a 3D game, which has to call objects such as rocks, trees, crows, pallets, walls, etc. AND their hitboxes, plus characters & killers, and their animations...I don't envy BHVR trying to work through this!

    https://forum.deadbydaylight.com/en/discussion/comment/2331887#Comment_2331887

    That does make it sound like a memory leak.

    Having just barely started coding in Python, yeah, I don't envy them either...

  • What is a memory leak anyway? How does code, or memory "leak"

  • @Edgars_Raven said:

    What is a memory leak anyway? How does code, or memory "leak"

    Check one of my posts further up; I pulled the wiki description of it.

    I'm guessing it's called a 'leak' because it works slowly over time to slow down the game, in the same way that it could be said a leak in a boat slowly sinks it.

  • And the student's name was Albert Einstein.

  • You can easily check this on your own.


    1. start up DBD
    2. open up your task manager if on windows/ whatever your OS calls it
    3. go to the performance tab
    4. look at the memory in use value, now it will probably be fluctuating a lot but we can call this the 'start' of when DBD is running
    5. Play a bunch of games
    6. check your memory again, if it is extremely bloated and you haven't run anything else odds are dbd has a memory leak


    Edit: This is assuming the leak is significant, technically the above might not catch a leak if it is extremely small/rarely occurs

  • @Carth said:

    You can easily check this on your own.

    1. start up DBD
    2. open up your task manager if on windows/ whatever your OS calls it
    3. go to the performance tab
    4. look at the memory in use value, now it will probably be fluctuating a lot but we can call this the 'start' of when DBD is running
    5. Play a bunch of games
    6. check your memory again, if it is extremely bloated and you haven't run anything else odds are dbd has a memory leak

    Edit: This is assuming the leak is significant, technically the above might not catch a leak if it is extremely small/rarely occurs

    And how would console check this?