Oom alloc#463
Conversation
|
Added another example that OOMs, hasn't been fixed yet, I'm working around it for my usecase by using unstable |
|
Thanks! |
|
Do you mean a comment explaining the last OOM file that was added? |
sftse
force-pushed
the
oom-alloc
branch
2 times, most recently
from
17fc324 to
1ffc325
Compare
|
I've added a FIXME to the function call that OOMs, if this was not what was meant please advise further. |
|
Curious whether you know anything about the unknown record types as mentioned in #462. |
| // tests/high_byte_string.xls contains a record type that | ||
| // cannot be found in the "By Number" 2.3.2 table | ||
| 0x00D6 => { |
There was a problem hiding this comment.
Tag 0x00D6 is RSTRING, i.e., rich multi-format strings.
There was a problem hiding this comment.
Is there a reference we can link?
There was a problem hiding this comment.
It doesn't seem to be mentioned in the Microsoft online docs (I have an old paper copy of the "Excel Developer's Kit" and it is in that. Next best would be to link to the OpenOffice docs for the "Microsoft Excel File Format": https://www.openoffice.org/sc/excelfileformat.pdf
3 participants
Was it intentional that
fn from_sparseassumes cells are in(row, col)order? This test example demonstrates this is not always the case and OOM allocates due to an overflow.Based on #462restructured history