It usually takes a while, but ...

Capture a "show memory summary", paying attention to the top row of values. The numbers you're interested in are "total memory" and "Largest Fragment"

Capture a series over time (frequently days, occasionally weeks ...)

I pasted them into a spreadsheet and charted the trends.

The errors you'll see logged with memory leaks are things like 'MALLOC: XXX process needs Y amount of memory, only zz bytes available'

Looking at the largest frag of memory will show that while there might be 27 Meg available, the largest frag (and hence, the largest memory segment available to provide for Process XXX) is 96k ... not enough.

The fact that you may see a declining memory pool is not enough to decide that there is, in fact, a memory leak ... that's merely a symptom. There can be good reasons for a declining mem pool ... you still have to look at the total memory utilization picture (show mem summ, show proc mem, etc).

If the IOS version you're using has been around for a while, chances are (as mentioned above) your best chance to find it (with any certainty) is scouring the Bug Sheets.

If your problem cycle is something on the order of minute-to-hours (versus days-to-weeks), then I'd be inclined to look at the interface hardware (flaky, static or lightning hit) or environment (too hot, inadequate air circulation, bad / low / weak / noisy power, etc)

Good Luck

Scott