Indeed was using an empty GlobalCEFApp.Cache, now it's fixed.
But this is what i found out :
When i first open my app, it creates 4 instances of TChromium. At this point, i have 10 instances of subprocess.exe on Windows task manager.
Now the user wants to change cookies dir, so i do the procedure as talked on this topic (close browser, free TChromium and creates new 4 instances of TChromium with the new cookies dir). Now i have 18 instances of subprocess.exe .
If i repeat the above procedure, i'll have 25 instances of subprocess.exe and so on.
It seems when you close the browser and free TChromium instance, its subprocesses are not closed, so the app keeps consuming more and more memory over time.
In my previous procedure of cookies dir changing , i did not have this issue because i closed the app, open it again and create the new TChromiums with the new cookie dir.
But this new procedure is a lot better because the user don't need to close the app anymore. BUT if this memory usage is normal, i'll need to go back to the previous procedure... Maybe i'm missing something
One thing i did not test yet, is to force close the subprocess.exe when i free TChromium, but this does not seem a good practice...
EDIT : I did the same test on the MDIBrowser demo and it does not have the same problem : when i close the mdi form , the subprocess is closed too. The difference between this demo and my app is that on the demo TChromium is created on a new MDI form, on my app its always on the main form. Could this be the an issue ?