bind 9.4.0 exit unexpectly with core dump

[Ding, Shiling]

We are running bind 9.4.0 on both our master and slave DNS servers, they are all RHEL. Recently, both named has been core dump after running about 2 weeks, the memory usage is about 600M. I checked into the core dump, it's wired and no trace available as following:

 [root at iamdying named]# gdb -core core.9493 
GNU gdb Red Hat Linux (6.3.0.0-1.132.EL3rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu".
Core was generated by `/usr/local/sbin/named'.
Program terminated with signal 11, Segmentation fault.
#0  0x080ae7cd in ?? ()
(gdb) trace
trace command requires an argument
(gdb) trace 0
No symbol table is loaded.  Use the "file" command.

Any other folks have similar issue? Or any suggestions? The reason we run latest is because 9.3.4 will hog cpu and we have to restart named to remediate the slow resolve.

Thanks.

shiling