Some workaround about out of memory problem

I find some workaround analyze about out of memory problem at http://blog.packet-foo.com/2013/05/the-notorious-wireshark-out-of-memory-problem/. In "Around #2", the author noted that "Most things Wireshark displays about a frame is stored in there. Additionally there are hash tables of reassembled data conversation".

1. I've found the fdata in process_packet(tshark.c), but it's freed at the bottom of the function. Are there any more fdatas not freed ?

2. Where are the hash tables that store reassembled data conversation ?

@kurt @Guy Harris

Thanks in advance.