hi guys,
thanks for the quick response...
hi winfinit,
in one thread i'm creating my data arrays as follows:
Code:
unsigned char* data = new unsigned char[size];
and then putting them in a queue.
in another thread, i'm dequeuing then delete'ing the arrays as follows:
As for freeing cache and memory through system calls, i would rather avoid that. I need my application to be cross-platform. Besides, when did memory reclamation - post deletion - become the application's responsibility?
hi jim mcnamara,
unfortunately i've been having a hard time running profilers because the front end of my application is Java (via JNI). Instead I've run my application 2 threads at a time and manually monitored /cat/{proc id}/status for memory issues. I know this is no guarantee, but i've been staring at this for a week and have yet to find an actual memory leak.
One thing I am starting to wonder is if this is related to multithreading. I'm using SDL to spawn the new threads which supposedly run in their own context yet still have access to data outside of it. Since i'm enqueuing in one thread and deleting in another, could that be the source of my problem??
Sheado