Closed Bug 625759 Opened 13 years ago Closed 13 years ago

Fennec does not start for me any more (Galaxy S Vibrant)

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
blocker

Tracking

(fennec-)

RESOLVED WORKSFORME
Tracking Status
fennec - ---

People

(Reporter: ehsan.akhgari, Assigned: blassey)

Details

(Keywords: dogfood)

Attachments

(1 file)

I had updated to the nightly version which enabled hw acceleration for all Android devices, and Fennec would just get stuck in the "loading" screen and would not start up.  Ever since, I can't start Fennec on my device.  I have tried wiping it out completely and reinstalling the latest nightly, and it would just show the the loading screen, with the "installing libraries" text which would change to "loading" soon afterwards, and would get stuck on that screen.

I'm using a Samsung Galaxy S Vibrant (GT-I9000M) which I have updated to Froyo recently.
tracking-fennec: --- → ?
OS: Mac OS X → Android
Hardware: x86 → ARM
Summary: Fennec does not start for me any more → Fennec does not start for me any more (Galaxy S Vibrant)
Assignee: nobody → blassey.bugs
tracking-fennec: ? → 2.0+
We're respinning nighlies now for a different issue, can you please retest when they become available?
Assignee: blassey.bugs → nobody
tracking-fennec: 2.0+ → 2.0b4+
Assignee: nobody → blassey.bugs
Attached file My logcat
I tested with the latest nightly, and the same thing happened again.  Here's my logcat, as requested by blassey on IRC.
The latest update is that when I closed the Fring app's background process, Fennec started to show a window which did not get painted in the content area or the location bar, and did not respond to user events.  I closed all other background processes, but they didn't have any effects on Fennec loading.
Seems like ehsan is the only one seeing this and no one else can reproduce. Some people have seen similar behavior, but they've all been resolved by a reinstall. Pushing this out from beta 4.
tracking-fennec: 2.0b4+ → 2.0+
(In reply to comment #4)
> Seems like ehsan is the only one seeing this and no one else can reproduce.
> Some people have seen similar behavior, but they've all been resolved by a
> reinstall. Pushing this out from beta 4.

Maybe this is an indication that we're doing something bad, which needs to be addressed without resorting to reinstalling.  Have any of the fennec developers ever encountered this?  Because that would give them a good chance at debugging the issue.
Regressed by bug 608042.
Depends on: 608042
Keywords: regression
(In reply to comment #6)
> Regressed by bug 608042.

I don't think that's true. I just installed the latest nightly on Ehsan's device and its working fine. He'll reopen if he sees it again.
Status: NEW → RESOLVED
Closed: 13 years ago
No longer depends on: 608042
Keywords: regression
Resolution: --- → WORKSFORME
I noticed this a lot of times today too.  Right now, it's reproducible on every start of Fennec.

I think Brad can take a look tomorrow at the office.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Can anyone reproduce this?  Builds run fine on my Vibrant (2.2)
tracking-fennec: 2.0+ → ?
Note to myself:

Here's how you debug Fennec on Android: <https://wiki.mozilla.org/User:Blassey/Notes/Android>
2.0-, since no one else can reproduce this
tracking-fennec: ? → 2.0-
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: