Closed
Bug 666146
Opened 14 years ago
Closed 6 years ago
An error popup is displayed when a download is resumed
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec-)
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| fennec | - | --- |
People
(Reporter: xti, Unassigned)
Details
(Keywords: testcase-wanted)
Attachments
(2 files)
Build id : Mozilla/5.0 (Android;Linux armv7l;rv:7.0a1)Gecko/20110621
Firefox/7.0a1 Fennec/7.0a1
Device: Motorola Droid 2
OS: Android 2.2
Steps to reproduce:
1. Open Fennec app
2. Go to http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android-r7/
3. Tap on fennec-7.0a1.multi.eabi-arm.apk
4. Go to Download Manager
5. Tap on Pause button
6. Tap on Resume button
7. Repeat steps 5&6 (between 2-10 times)
Expected result:
The downloading process is paused or resumed with any errors, no matter how many times step 7 is repeated.
Actual result:
After step 7, an error popup is displayed.
Also in console, the following error occurs:
Error: uncaught exception:[Exception... "Component returned failure code: 0x8000fff (NS_ERROR_UNEXPECTED) [nsIDownloadManager.pauseDownload]" nsresult: "0x8000fff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://browser/content/downloads.js :: dv_pauseDownload :: line 404" data: no]
| Reporter | ||
Comment 1•14 years ago
|
||
Updated•14 years ago
|
Keywords: testcase-wanted
Comment 2•14 years ago
|
||
I can see the error popup occuring, but not the js error in the error console.
Comment 3•14 years ago
|
||
I was able to reproduce the error popup on Mozilla/5.0 (Android;Linux armv7l;rv:9.0a1)Gecko/20110822 Firefox/9.0a1 Fennec/9.0a1
Device: HTC Desire
OS: Android 2.2
The error popup appears when the steps from bug are followed, and also, when the download is paused and then resumed after >10 minutes.
Note: I didn't see any errors in the error console.
| Reporter | ||
Updated•14 years ago
|
tracking-fennec: --- → ?
Updated•14 years ago
|
tracking-fennec: ? → -
Comment 4•6 years ago
|
||
Closing all opened bug in a graveyard component
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•