Comment 28 for bug 1690519

Thx for your test, aso of differnte SDL Implementation our result will vary.
Just found that I can insall valgrind via MacPorts.
What I extracted from the logs:

==1355== Syscall param writev(vector[...]) points to uninitialised byte(s)
...
==1355== by 0xC868C2: WLApplication::WLApplication(int, char const* const*) ==1355==
...
Uninitialised value was created by a stack allocation
-> this _can_ caue a random crash, mmh

those memory leaks are not good, but will not cause a crash.
We should open a kind of clenaup bug for those, too.

Ill try that valgrind once I have some spare time again, thx for your checks.