-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Memory Leak #2343
Comments
There are memory leaks, but it's hard to fix out exactly where they are. They may be present in the Qt/WebKit bindings itself (which should hopefully be fixed with the 0.13 upgrade) or in the custom Qt patches (which I'll review for 0.13). The simplest solution is to use a separate process and periodically restart it if the leaks go very high. |
Hi Ashish, thanks for the response. Another post from Sept 2014 mentions the deleteLater() method, do you not Phil |
Yeah, but those were necessary for avoiding some crashes according to @pruiz. I've not really explored that in detail -- when you build in debug mode, it prints the leaks in WebKit after conversion completes. That might be a good start to identify where the problem is, but never got time to do that 😦 |
I understand ... thanks anyway, for now Im going to take your advice and Cheers ! Phil |
Can you try if 9fa4695 improves things? See the commit message for more details. |
@pienaarp: were you able to try the above commit? |
Hi Ashish, Is this still an open issue? As I am experiencing the same memory leaks with v 12.4.0... Thank you for a gr8 app ;) Dirk |
Built wkhtmltopdf 0.12.2.4 with the flag -debug and executed conversion HTML file into PDF under valgrind-3.11.0. The command line:
The summary of report:
|
Hello,
I am using Wkhtmltopdf which is very nice, thank you. The output is very clear.
However there seems to be a memory leak, I think it may be caused by calls to 'wkhtmltopdf_convert', and for me the amount varies between 20k - 60k.
Are you aware of this ? Do you have any advice to avoid ? I am definitely calling wkhtmltopdf_destroy_converter.
Many thanks,
-Phil
The text was updated successfully, but these errors were encountered: