Robotics Service Bus » RSBag

The purpose of this issue is documenting the current situation. There is no immediate fix except improving error messages.

When reading corrupt TIDELog files, several kinds of seemingly unrelated errors can occur. This happens when an incorrect size value is read from a file and used in an allocation.

All RSBag tools which read files are affected (at the time of writing bag-cat, bag-play, bag-merge).

On 32-bit and 64-bit platforms, the problem can look like this:

Heap exhausted during allocation: 815529984 bytes available, 1818326592 requested.
 Gen StaPg UbSta LaSta LUbSt Boxed Unboxed LB   LUB  !move  Alloc  Waste   Trig    WP  GCs Mem-age
   0:  3579     0  5239     0    25     0   912     0     0 30521264 182352 53687091    0   0  0.0000
   1:     0     0     0     0     0     0     0     0     0        0     0 53687091    0   0  0.0000
   2:  4217  4218     0     0   305    29     0   338   109 21846960 173136  2000000  268   0  0.0000
   3:     0     0     0     0     0     0     0     0     0        0     0  2000000    0   0  0.0000
   4:     0     0     0     0     0     0     0     0     0        0     0  2000000    0   0  0.0000
   5:     0     0     0     0     0     0     0     0     0        0     0  2000000    0   0  0.0000
   6:     0     0     0     0  2686   789     0     0     0 113868800     0  2000000 2311   0  0.0000
   Total bytes allocated    = 166237024
   Dynamic-space-size bytes = 1073741824
GC control variables:
   *GC-INHIBIT* = false
   *GC-PENDING* = false
   *STOP-FOR-GC-PENDING* = false
Heap exhausted (no more space for allocation).
There are still 815529984 bytes available; the request was for 1818326592 bytes.

PROCEED WITH CAUTION.

On 32-bit platforms (and very unlikely on 64-bit platforms) the problem can also look like this:

The value 1818326576 is not of type (UNSIGNED-BYTE 29).