Closed Bug 732709 Opened 14 years ago Closed 13 years ago

HTML5 regression: MediaFire forever stuck on Queued when HTML5 instant upload feature enabled

Categories

(Tech Evangelism Graveyard :: English US, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: danialhorton, Unassigned)

References

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0 Build ID: 20120303031033 Steps to reproduce: Logged into MediaFire (Account required, the instant upload feature is not enabled on free uploads) Attempted to upload a file to my account Actual results: the file was forever stuck on queued Expected results: file should have uploaded
Summary: HTML5 regression: MediaFire forever stuck on Queded when HTML5 instant upload feature enabled → HTML5 regression: MediaFire forever stuck on Queued when HTML5 instant upload feature enabled
ignore the user agent, i had a 4.0 agent set for checking another site, the bug was reproduced in a clean profile however, so its unrelated.
Can you please try to find the regression range ? Either by downloading nightly builds or with a tool like mozregression.
i'll check a few builds from around the 20th of feb, around that time is when this started happening apparently.
first occuring in 20120218
Thanks ! Can you post the build rev from the first bad and the last good one ? The rev is the URL after "build from" in about:buildconfig
im kinda finding it hard to see why that buildset would break it, did any merges happen between the 17th and 18th of february?
I also fail to see something that would explain this in http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2271cb92cc05&tochange=550779e6bab4 Have you already tried the safemode and a new profile ? Do you see errors in the error console ?
comment 1 Matti. the new simple bug reporter template makes it easy to leave out important info in the initial post.
i would've been quick to blame Bug 713936, but SSL was indeed disabled with my tests. the 2 builds i tested were launched from profile manager into a temporary profile. the 2 PGO green merges from inbound however, do scream potential cause to me. PGO can break things in wonderful ways......
i left it out of my initial post before because i usually didn't notice it with the test files i was using, but when you first drop a file onto the mediafire site it validates or verifies the file first This performs some kind of hash check to see if the file already exists on Mediafire and if it does it is instead copied into your account instead of uploaded. It never performs this step, hanging at the queued phase after the affected buildset.
Regression window(m-c) Works: http://hg.mozilla.org/mozilla-central/rev/2271cb92cc05 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0a1) Gecko/20120216 Firefox/13.0a1 ID:20120216192149 Fails: http://hg.mozilla.org/mozilla-central/rev/08e55f36b731 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0a1) Gecko/20120217 Firefox/13.0a1 ID:20120217031232 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2271cb92cc05&tochange=08e55f36b731 Regression window(m-i) Works: http://hg.mozilla.org/integration/mozilla-inbound/rev/7e90fe61000f Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0a1) Gecko/20120215 Firefox/13.0a1 ID:20120216000354 Fails: http://hg.mozilla.org/integration/mozilla-inbound/rev/69cb70c3a1e9 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0a1) Gecko/20120215 Firefox/13.0a1 ID:20120216022449 Pushlog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=7e90fe61000f&tochange=69cb70c3a1e9 Triggered by: 1f99e7a087c1 Matthew Schranz — Bug 725289 - Removed moz prefix in Blob.mozSlice. r=sicking
Blocks: 725289
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
Component: Untriaged → DOM
Product: Firefox → Core
QA Contact: untriaged → general
Version: Trunk → 13 Branch
Assignee: nobody → english-us
Component: DOM → English US
Product: Core → Tech Evangelism
QA Contact: general → english-us
Version: 13 Branch → unspecified
thanks Alice
any response?
No response.
I bumped the ticket on Mediafire support forum.
I submitted a request for mediafire devs to get in touch here as well. will give them a day or so before nudging it again.
"Hello Danial, Thank you for bringing this to our attention. I have forwarded all relevant information to our development department so they can review this bug. As soon as we have something to report we'll let you know."
Good! To be clear: Instant Upload (My Account > Upload Options > HTML5 Uploader is Enabled > Instant Uploads: ON) doesn't work with Firefox 13 because Mediafire is using Blob.mozSlice that has been unprefixed recently in Firefox 13. Result: uploads stay queued and local hashing runs in infinite loop.
@all, update to MediaFire.com code yesterday is believed to fix this.
Verified: Fixed :)
Closing this then.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.