[ARM]firefox can not exit after downloading

RESOLVED INVALID

Status

()

Firefox
General
--
major
RESOLVED INVALID
8 years ago
8 years ago

People

(Reporter: pangdae, Unassigned)

Tracking

3.5 Branch
ARM
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; zh-CN; rv:1.9.1.0) Gecko/20090623 SUSE/3.5.0-5.1 Firefox/3.5
Build Identifier: Mozilla/5.0 (X11; U; Linux armv7l; en-US; rv:1.9.1) Gecko/20090703 Shiretoko/3.5

use the firefox3.5 download anything, download can finish, then close all the firefox window, the firefox window can disappear, but the process still can find in the `ps ax` command, use the 'strace -p' to attach it , get the futex information.

This problem can not happen in the 3.5b4.

Reproducible: Always
(Reporter)

Updated

8 years ago
Hardware: Other → ARM
Version: unspecified → 3.5 Branch
(Reporter)

Comment 1

8 years ago
some error information in debug log:

WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80520015: file nsXREDirProvider.cpp, line 1151
pldhash: for the table at address 0x41af7560, the given entrySize of 48 probably favors chaining over double hashing.
WARNING: NS_ENSURE_TRUE(mHiddenWindow) failed: file nsAppShellService.cpp, line 396
WARNING: NS_ENSURE_TRUE(browserChrome) failed: file nsDocShell.cpp, line 9291
WARNING: Something wrong when creating the docshell for a frameloader!: file nsFrameLoader.cpp, line 902
WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file nsFrameLoader.cpp, line 926
WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file nsFrameLoader.cpp, line 182
WARNING: recurring into frame construction: 'mPresContext->mLayoutPhaseCount[eLayoutPhase_FrameC] == 0', file ./nsPresContext.h, line 1026
WARNING: recurring into frame construction: 'mPresContext->mLayoutPhaseCount[eLayoutPhase_FrameC] == 0', file ./nsPresContext.h, line 1026
pldhash: for the table at address 0x461a1758, the given entrySize of 52 probably favors chaining over double hashing.
WARNING: recurring into frame construction: 'mPresContext->mLayoutPhaseCount[eLayoutPhase_FrameC] == 0', file ./nsPresContext.h, line 1026
JavaScript strict warning: chrome://mozapps/content/downloads/downloads.js, line 401: reference to undefined property window.arguments
JavaScript strict warning: chrome://mozapps/content/downloads/downloads.js, line 401: reference to undefined property window.arguments
JavaScript error: chrome://mozapps/content/downloads/downloads.js, line 401: window.arguments is undefined
^G###!!! ASSERTION: aFileExt shouldn't start with a dot: 'aFileExt[0] != '.'', file ./unix/nsGNOMERegistry.cpp, line 120
^G###!!! ASSERTION: aFileExt shouldn't start with a dot: 'aFileExt[0] != '.'', file ./unix/nsGNOMERegistry.cpp, line 120
^G###!!! ASSERTION: Oops!  You're asking for a weak reference to an object that doesn't support that.: 'factoryPtr', file nsWeakReference.cpp, line 109
JavaScript error: , line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIObserverService.removeObserver]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://mozapps/content/downloads/downloads.js :: Shutdown :: line 430"  data: no]
(Reporter)

Comment 2

8 years ago
use the command` export NSPR_LOG_MODULES=all:5` 
please check the attachment log.nspr
(Reporter)

Comment 3

8 years ago
the last some lines for log.nspr
-----------------------------------------------------------------------------------------
1090503888[41317060]: DOCSHELL 41310e00 destroyed
1090503888[41317060]: DocLoader:41310e00: Stop() called
1090503888[41317060]: DocLoader:41310e00: deleted.
1090503888[41317060]: nsObserverService::NotifyObservers(profile-change-net-teardown)
1090503888[41317060]: receiving network teardown topic
1090503888[41317060]: nsHttpHandler::Observe [topic="profile-change-net-teardown"]
1090503888[41317060]: nsHttpHandler::StopPruneDeadConnectionsTimer
1155527824[4143a950]: waiting for 212
1090503888[41317060]: nsHttpAuthCache::ClearAll
1090503888[41317060]: nsHttpConnectionMgr::Shutdown
1090503888[41317060]: STS dispatch [412675c0]
1090503888[41317060]: THRD(413ada60) Dispatch [412675c0 0]
1090503888[41317060]: EVENTQ(413ada84): notify
1155527824[4143a950]: Timer thread woke up -83ms from when it was supposed to
1155527824[4143a950]: THRD(413ad060) Dispatch [41267600 0]
1155527824[4143a950]: EVENTQ(413ad084): notify
1155527824[4143a950]: waiting for 447
1155527824[4143a950]: Timer thread woke up -84ms from when it was supposed to
1155527824[4143a950]: THRD(413ad060) Dispatch [41267620 0]
1155527824[4143a950]: EVENTQ(413ad084): notify
1155527824[4143a950]: waiting for 2137
1155527824[4143a950]: Timer thread woke up -62ms from when it was supposed to
1155527824[4143a950]: THRD(413ad060) Dispatch [41267640 0]
1155527824[4143a950]: EVENTQ(413ad084): notify
1155527824[4143a950]: waiting for 1318
1155527824[4143a950]: Timer thread woke up -73ms from when it was supposed to
1155527824[4143a950]: THRD(413ad060) Dispatch [41267720 0]
1155527824[4143a950]: EVENTQ(413ad084): notify
1155527824[4143a950]: waiting for 2773
1155527824[4143a950]: Timer thread woke up -84ms from when it was supposed to
1155527824[4143a950]: THRD(413ad060) Dispatch [413d57a0 0]
1155527824[4143a950]: EVENTQ(413ad084): notify
1155527824[4143a950]: waiting for 1387
1155527824[4143a950]: Timer thread woke up -84ms from when it was supposed to
1155527824[4143a950]: THRD(413ad060) Dispatch [413d5920 0]
1155527824[4143a950]: EVENTQ(413ad084): notify
1155527824[4143a950]: waiting for 825
1155527824[4143a950]: Timer thread woke up -84ms from when it was supposed to
1155527824[4143a950]: THRD(413ad060) Dispatch [41af0dc0 0]
1155527824[4143a950]: EVENTQ(413ad084): notify
1155527824[4143a950]: waiting for 656
1155527824[4143a950]: Timer thread woke up -84ms from when it was supposed to
1155527824[4143a950]: THRD(413ad060) Dispatch [41af0de0 0]
1155527824[4143a950]: EVENTQ(413ad084): notify
1155527824[4143a950]: waiting for 511460
(Reporter)

Comment 4

8 years ago
still nobody care the bug?
(Reporter)

Comment 5

8 years ago
this is not mozilla priblem
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.