[Bug 54458] vbscript memory leaks in Global_Split

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=54458

--- Comment #3 from Nikolay Sivov  ---
For tests we only need to make sure that Split() is tested at all. Then to
detect leaks the tests are executed using some leak detection tool. With wine I
know people are using valgrind on Linux. I don't know how well it works with
current wine/valgrind. But basically, there is no direct support to detect such
issues in our tests, you only need to make sure functionality is executed, so
the test can potentially trigger the leak.