Commented Unassigned: How to find the source of a VLD-reported leak without meaningful stack trace? [10614]

In some cases when using VLD (Visual Leak Detector) all I get in the stack trace is a heap memory allocation call which isn't very useful. For example:

```
---------- Block 350507 at 0x10842178: 400 bytes ----------
Leak Hash: 0x17EB3636, Count: 1, Total 400 bytes
Call Stack (TID 12608):
ntdll.dll!RtlAllocateHeap()
Data:
00 00 00 00 40 31 00 00 00 00 00 00 00 00 00 00 ....@1.. ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
```
How to find the source of a leak in this case?

Can other information in this entry help me somehow?
Comments: i did change stack traversing to safe. it took ages but eventually i learnt it's issue with openssl. Thanks for suggestion - former sounds interesting, could be much quicker than what i did. Later is a different issue, I have encountered it in the search as well.