Bug 273756 - Taglib enters infinite loop when trying to find tags in maximum length wave files
Summary: Taglib enters infinite loop when trying to find tags in maximum length wave f...
Status: RESOLVED WORKSFORME
Alias: None
Product: taglib
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 1.7
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Scott Wheeler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-20 22:07 UTC by J Barlow
Modified: 2023-01-17 05:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description J Barlow 2011-05-20 22:07:09 UTC
Version:           1.7 (using Devel) 
OS:                Linux

Create a .wav file that is larger than 2 GB in size.  When taglib tries to read the file, it enters an infinite loop, repeating the following error message:

TagLib: ByteVectorMirror::toNumber<T>() -- data is empty, returning 0

(A 24-bit stereo wave file at 2 GB is under two hours long, so this is a realistic file size.)

Reproducible: Always

Steps to Reproduce:
Create a 2 GB wave file with a valid wave file header.
Run: ./tagreader huge.wav
Or run: ./tagreader_c huge.wav

Actual Results:  
Infinite loop with error message
TagLib: ByteVectorMirror::toNumber<T>() -- data is empty, returning 0


Expected Results:  
Produce tag data :)

Here is the wave file's header.  All the rest of the data can be zeros.  The exact length of my wave file was 2147483647 (2^31 - 1).

I can provide the compressed wave file if desired.

00000000  52 49 46 46 f7 ff ff 7f  57 41 56 45 66 6d 74 20  |RIFF....WAVEfmt |
00000010  10 00 00 00 01 00 02 00  44 ac 00 00 10 b1 02 00  |........D.......|
00000020  04 00 10 00 64 61 74 61  d3 ff ff 7f              |....data....|
0000002c
Comment 1 Andrew Crouthamel 2018-11-05 03:15:21 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-17 05:03:48 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-18 08:18:19 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2023-01-02 05:27:11 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-01-17 05:18:26 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!