Brian has just committed a large (~10k lines in the patch file) patch that I
wrote that removes the arbitrary limits on array sizes. The major change
with this is that these arrays must now be dynamically allocated. This is
the responsibility of driver writers to ensure that the correct memory is
allocated and freed for each message you send. I have updated all of the
drivers that I could in player, but many could not be tested without the
hardware, some wont even compile without special libraries. These changes
should reduce the memory footprint of player some what, particularly if you
are using devices like low resolution cameras (where as the data packets are
big enough for high res cameras)
What this means to player developers/users:
1) It needs lots of testing, if you have access to specific hardware please
try out CVS HEAD, this will shortly become player 2.1 rc1.
2) Watch out for memory leaks and corruptions, please let us know about them
(gdb backtraces/valgrind logs or even better patches are appreciated)
3) With the client libraries most proxies should be similar, one or two may
have changes to fit the new structure anywhere where you need to worry about
freeing memory should be clearly marked in the documentation.
I think that is about all you need to know, please let us know how testing
it goes, whether it is noticeably leaner or just plain old doesn't work...
This email is intended for the addressee only and may contain privileged
and/or confidential information
Get latest updates about Open Source Projects, Conferences and News.