mitchell at kde.org
Tue Aug 3 14:10:40 CEST 2010
Recently we had a bug report where someone had a 500MB WAV file that had
somehow been overwritten with all zeros.
When TagLib tries to read this it uses an ever-increasing amount of
memory, including via the tagreader example. Yes, this file is totally
corrupt, but it'd be nice if it could bail nicely in such a
circumstance, if at all possible. If this is indeed a bug I can open a
bug report; if there is no real way for TagLib to deal with this
gracefully then let me know and I won't open one.
The file is at https://bugs.kde.org/show_bug.cgi?id=236052#c40 if you'd
like to test it.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/taglib-devel/attachments/20100803/cc2d7147/attachment.sig
More information about the taglib-devel