1435742 - mp3 duration bug

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[odruslan]

Attachment: teen_spirit_14s1.wav

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36

Steps to reproduce:

var fileBase64 // readed file by new FileReader().readAsDataURL(file)

var audio = new Audio(newVal);
 audio.onloadedmetadata = function () {
  console.log( audio.duration );
};


Actual results:

Chrome return 14s
Firefox return >54h


Expected results:

Firefox must return 14s

Comment 1

[:Gijs (back August 25; he/him)]

Not a security bug that needs to be hidden.

Comment 2

[Marius Coman [:mcoman], Ecosystem QA]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Firefox: 60.0a1, Build ID 20180207100355

I've tried to use the code from the description, in the "Web Console" and the "ReferenceError: newVal is not defined" error was displayed. Also I've tried to use the code in the "Scratchpad" and the same error was displayed again. 
I've tested this issue on Ubuntu 14.04 x64, Windows 10 x64 and Mac 10.12.

In order to move the issue forward, could you please told us where should we use the code from the description, or better, if is possible, can you create a simple test case on "https://jsfiddle.net"?

Comment 3

[alco]

Adding that I tested with the following code and got the same correct answers in both browsers.

var audio = new Audio("some_local_file.wav");
console.log(audio.duration);

Comment 4

[odruslan]

Bug reproduced only with attached file

Comment 5

[Marius Coman [:mcoman], Ecosystem QA]

Hi Odruslan, 

Could you please add some actionable steps to reproduce, answer the questions in comment 2 and post a self sustained test case where the issue can be observed? 

As I am unable to reproduce the issue you are having, it can not be moved forward and will most likely be closed as Incomplete.

Comment 6

[Marius Coman [:mcoman], Ecosystem QA]

Marking this as Resolved - Incomplete due to the lack of response from the reporter.
If anyone can still reproduce it on the latest versions, feel free to reopen the issue and provide more information.