Correct potenital locking issue in msg allocation
The message allocation when pulling a buffer from the free pool could
potentially fail to own the lock. This was causing core dumps for
multi-threaded processes (e.g. those using the Go wrapper).
Version bump to 4.5.0 to move away from the previous release of
4.4.*.
Issue-ID: RIC-732
Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: I9abc7f64391d0292c5ba1323713040faedb569a1
(cherry picked from commit
ce1c741c01e8387cb095dac5e36a4d8ad91d006d)