Jump to content
  • Advertisement
Sign in to follow this  
Knight52

Memory leak when doing multiple thread

This topic is 2125 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I know how bad it is to go multi-threading, but I don't know how else I will load stuff behind the loading screen.
No memory leaks when I do single thread, but when I create another thread to handle that same function, I got memory leaks. That function handles some Direct3D loading too. Do I have to release something before exiting the thread?

Share this post


Link to post
Share on other sites
Advertisement
check if the directx functions you are using are thread-safe
without any code, it's hard to help you

as you should know, in threading, all threads can access the same (shared) memory
without mutex locks, you can't be certain that the same memory isnt accessed or overwritten by threads at the same time
one bad example is: if you allocate memory at the same time on both threads, both pointers could end up with the same value! (memory offset)
threads don't necessarily start in the order you started them in
they don't execute at the same speed
just google threads! theres LOTS you need to know about them before you can start using them in a game!!
start using threads in a small test project and find out what you can and can't do!

Share this post


Link to post
Share on other sites

I know how bad it is to go multi-threading, but I don't know how else I will load stuff behind the loading screen.
[/quote]
Have you tried non-blocking or asynchronous I/O?

Share this post


Link to post
Share on other sites
check if the directx functions you are using are thread-safe without any code, it's hard to help you as you should know, in threading, all threads can access the same (shared) memory without mutex locks, you can't be certain that the same memory isnt accessed or overwritten by threads at the same time one bad example is: if you allocate memory at the same time on both threads, both pointers could end up with the same value! (memory offset) threads don't necessarily start in the order you started them in they don't execute at the same speed just google threads! theres LOTS you need to know about them before you can start using them in a game!! start using threads in a small test project and find out what you can and can't do!


I know how bad it is to go multi-threading, but I don't know how else I will load stuff behind the loading screen.
Have you tried non-blocking or asynchronous I/O? [/quote]

I've created a mutex lock, still doesn't fix the leaks. I've tried WM_TIMER which I understand it's one of asyn io processes, doesn't fix the leak either. So I don't think it's multi-threading resource issue.
Here's the some sort of algorithm. Hope this will help.


Retrieve info
if player is initialized.
{
separate the player and equipments from resource pool.
}
Flush the resource pool. This includes Skybox primitives and texture, object's model and animation, terrain, and lights' shadow maps.
Open the file
if(file == null)
{
Messagebox ("cannot open file")
exit
}
Load new resources by reading info from the file.
if player is initialized
{
add the player and equipments back to resource pool
}
else
{
initialize player and add it to the resource pool
}
delete file.
hide loading screen.
release mutex
close mutex
Edited by Knight52

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!