bug reading certain wav file

[Nick Shaforostoff]

i confirm this. the problem is that all chunks of wav file are stored in memory,
whereas only first few of them are needed, and only of certain type ('id3 ', 'riff').

i can send you the patch with the fix, but it is not tested for the case when tag data is written back to the file.

 --- Исходное сообщение ---
 От кого: " Jens Nachtigall" <nachtigall at web.de>
 Кому: taglib-devel at kde.org
 Дата: 5 октября 2011, 16:44:48
 Тема: Re: bug reading certain wav file
 


> Dear all,
> 
> using mixxx (a dj program using taglib, mixxx.org) i noticed a bug [1]
> Actually this turns out to be a bug in taglib (amarok also crashes when
> loading this very wav file).
> 
> It is very easy to reproduce, just do
> taglib-1.7/examples/tagreader ~/tmp/09_15_2011-21h_14m_33s.wav
> 
> The file can be found here:
> http://www2.informatik.hu-berlin.de/~nachtiga/09_15_2011-21h_14m_33s.wav
> 
> This wav file causes tagreader to allocate about 2GB of memory until it
> causes a SIGABRT. Any solution / direction for debuggin? Should I open a
> bug?
> 
> 
> ps I am not on the list, so please CC me.
> 
> [1] https://bugs.launchpad.net/mixxx/+bug/851737
> _______________________________________________
> taglib-devel mailing list
> taglib-devel at kde.org
> https://mail.kde.org/mailman/listinfo/taglib-devel