I was able to reproduce the leak using one of the demo apps. Steps to reproduce:
- Click Start and once the animation starts, click Stop. Wait 30s or so for memory usage to settle - it now hovers around 320Mb.
- Change the currentAngle value in the code editor to any random number between 0 and 360.
- Click Start again and immediately click stop once the animation starts. Wait 30s for memory usage to settle. It now sits at about 410Mb.
If you repeat steps 3 & 4 multiple times, the memory used by the application grows by anywhere from 30Mb to 130Mb…and it never seems to be released no matter how long you leave the application running.
That was fast! A hotfix would be extremely useful if you can provide one.
Thanks for the excellent support!
Will prepare a fix and will send it to you ASAP. We’ve also added option to HostItem: GenerateDescription, which causes d.ts generator to include JavaDocs in the output file, which then are used to provide descriptions for code completion.
Will include this functionality to the hot fix as well.
Please try this hotfix:
It should address issues with cashing d.ts files, memory leak and also allow to generate JavaDocs (you would need to set GenerateDescriptions option for the assembly host item):
Let me know if it works for you.
The caching of the file and memory leak are fixed.
The GenerateDescriptions option also works - but only for System.Object methods. So things like Equals(), GetHashCode(), GetType(), ToString() etc all have JavaDocs text now being generated in the .d.ts file, but none of the /// style comments in front of my methods are coming across. That part isn’t that important though so I don’t need another hotfix for that.
Thanks very much for your help!
Thank you for confirming that the issue with memory leak has been resolved.
With the documentation, it seems to work fine on our tests, provided that you have .xml file generated next to the dll. On our tests we compiled dll with Documentation File option on, so xml-comment descriptions from source are translated to the xml document. Then this xml document is picked up during generation of d.ts file.
I’ve uploaded our test dll alongside with generated d.ts file here:
If it does not work the same on your tests, could I ask you to send us cut-down sample where it can be reproduced?
Apologies - user error. Once I generated my DLL with Documentation File turned on the hints are now working as expected. Thanks very much!