Closed
Bug 579370
Opened 15 years ago
Closed 15 years ago
Crash at [@ libxul.so@0x6ce94c] when accessing your tabs from another computer
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(fennec2.0a1+)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
fennec | 2.0a1+ | --- |
People
(Reporter: aakashd, Unassigned)
References
Details
(Keywords: crash)
Crash Data
Attachments
(1 obsolete file)
Build Id:
Mozilla/5.0 (X11; U; Linux armv71; Nokia N900; en-US; rv:2.0b2pre) Gecko/2010716 Namoroka/4.0b2pre Fennec/2.0a1pre
Report:
http://crash-stats.mozilla.com/report/index/1209ee7a-aa44-423f-a6ac-6c2332100716
Steps to Reproduce:
1. Connect to Weave and Sync your tabs
2. Go to about:home
3. Click on "Tabs from your other computers"
4. After the page has loaded, slide to the right to open the tabs sidebar
5. Go back to the tab with about:home loaded
6. Click on "Tabs from your other computers" again
7. Wait for the page to load
Actual Results:
Crash at @ libxul.so@0x6ce94c
Comment 2•15 years ago
|
||
These STR were fixed by bug 578711, but the underlying crash/failure still
remains as bug 579346.
Since this bug has a crash, but not a stack sadly, we'll dupe to this one.
New STR:
0. Configure Fennec with a Weave account
1. Enter "about:sync-tab"
2. After that page loads, open a new tab.
3. Repeat step 1
4. Crash
Comment 3•15 years ago
|
||
Should be "about:sync-tabs"
Severity: major → critical
Keywords: crash
Summary: Crash at @ libxul.so@0x6ce94c when accessing your tabs from another computer → Crash at [@ libxul.so@0x6ce94c] when accessing your tabs from another computer
Updated•15 years ago
|
tracking-fennec: ? → 2.0a1+
Comment 4•15 years ago
|
||
I see the attached backtrace from the content process on desktop linux fennec.
Assignee: nobody → josh
Comment 5•15 years ago
|
||
I also see the a bunch of errors like the following:
###!!! ASSERTION: must be a file:// url: 'Error', file /home/t_mattjo/src/firefox/mobilebase/netwerk/base/src/nsURLHelper.cpp, line 200
JS Component Loader: ERROR (null):0
uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIProperties.get]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///home/t_mattjo/src/firefox/mobilebase/fennec-dbg/dist/bin/components/nsHandlerService.js :: anonymous :: line 909" data: no]
JS Component Loader: ERROR resource://services-sync/service.js:59
Error: resource://services-sync/engines/clients.js - Could not get symbol 'Clients'.
JavaScript error: , line 0: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: about:sync-tabs :: <TOP_LEVEL> :: line 20" data: no]
Comment 6•15 years ago
|
||
Actually I believe this backtrace is for a completely different crash for which I have filed bug 583487.
Updated•15 years ago
|
Attachment #461787 -
Attachment is obsolete: true
Comment 7•15 years ago
|
||
I cannot reproduce a crash on desktop fennec on linux, but the errors in comment 5 are still reproducible.
Updated•15 years ago
|
Assignee: josh → nobody
Comment 9•15 years ago
|
||
I'm not experiencing a freeze when doing steps 1-3 in comment 0. This happens when starting up fennec from scratch, and clicking tabs from other computers as the first step.
Its so bad, i need to hard boot my device. :(
Comment 10•15 years ago
|
||
not => now(In reply to comment #9)
> I'm not experiencing a freeze when doing steps 1-3 in comment 0. This happens
> when starting up fennec from scratch, and clicking tabs from other computers as
> the first step.
>
> Its so bad, i need to hard boot my device. :(
not => now
Comment 11•15 years ago
|
||
The steps in comment 0 are guaranteed to fail right now until bug 583777 is fixed.
Comment 12•15 years ago
|
||
Marking this WFM unless I hear otherwise.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Comment 13•15 years ago
|
||
Nevermind, Tony tells me that this is still a freeze on devices.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 14•15 years ago
|
||
freezes or crashes?
Comment 15•15 years ago
|
||
If aakash can reproduce the crash, we should keep this bug open. my situation freezes with the steps in comment 0, but thats not the original bug here.
i'll be happy to file another bug if that clarifies things.
Reporter | ||
Comment 16•15 years ago
|
||
This WFM on build:
Mozilla/5.0 (X11; U; Linux armv71; Nokia N900; en-US; rv:2.0b4pre) Gecko/20100811 Namoroka/4.0b4pre Fennec/2.0a1pre
Status: REOPENED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•14 years ago
|
Crash Signature: [@ libxul.so@0x6ce94c]
You need to log in
before you can comment on or make changes to this bug.
Description
•