Closed Bug 707467 Opened 14 years ago Closed 14 years ago

Tab state corruption and crash

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: CoJaBo-Bugzilla, Unassigned)

Details

(Keywords: crash, reproducible, Whiteboard: [native-crash])

Attachments

(1 file)

29.17 KB, text/plain
Details
I've noticed this state-corruption issue fairly frequently, but this is the first time that has crashed (uncertain if the crash is actually related to it). The events leading up to this were, roughly- Had some Wikipedia page open from prior. Opened a Youtube video from m.facebook.com in new tab. Opened a comment page in new tab. At this point, the current page and the Wikipedia page were replaced with the contents and url of the newly opened comment tab. I switched to the youtube video, which showed a gray screen, then selected the url and hit enter (to reload- refresh generally fails in this situation). The page began to load, then the browser abruptly force-closed. Logcat is attached, shows a memory-allocation error.
Attached file logcat
I/GeckoTab(17768): Updated url: http://m.youtube.com/#/watch?desktop_uri=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dppmzx6B1X8k%26feature%3Dyoutu.be&feature=youtu.be&v=ppmzx6B1X8k&gl=US for tab with id: 1 I/GeckoApp(17768): Got message: Content:SecurityChange I/GeckoApp(17768): Security Mode - unknown I/GeckoApp(17768): Got message: Content:StateChange I/GeckoApp(17768): State - 196612 I/InputConnectionWrapper.ICC( 1786): Got out-of-sequence callback 26692 (expected 26693) in setExtractedText, ignoring. I/GeckoApp(17768): stop I/GeckoApp(17768): destroy D/GeckoFavicons(17768): Closing Favicons database I/Process (17768): Sending signal. PID: 17768 SIG: 9 I/WindowManager( 1720): WIN DEATH: Window{40556a88 org.mozilla.fennec/org.mozilla.fennec.App paused=false} I/ActivityManager( 1720): Process org.mozilla.fennec (pid 17768) has died. I/WindowManager( 1720): WIN DEATH: Window{40794818 SurfaceView paused=false} Dupe of bug 704162?
The crash is reproducible, tho no specific steps seem to cause it. What I'm doing is going to m.Facebook.com and opening various links in new tabs, including comment pages and external links. Almost immediately, Fennec will start mixing up the tab contents. Selecting the URL and hitting enter will sometimes load the correct Paige, doing this for ten minutes or so will inevitably lead to a crash, almost always when trying to reload one of the external links i opened. This doesn't look like bug 704162 to me- The last crash was on a non-Flash site and i don't think my device even has Flash installed/enabled. I'll attach that logcat later today, it shows the same vm mammary error.
Severity: normal → critical
Keywords: crash
Hardware: All → ARM
Whiteboard: [native-crash]
This is a reproducible crash with steps- 1. Go to http://m.facebook.com/theonion - wait for the page to stop loading. 2. Long press Home at the top of the page. Press Open link in new tab - Wait for the page to stop jumping around. 3. Find a link post ("The Onion shared a link") and long press the Comments link below it ("123 Comments"). Press Open link in new tab - Wait for the page to stop jumping around. 4. Three tabs should be open, in order, "The Onion", "Facebook" and "Comments". Switch to the Comments tab. 5. Click the link and wait for the page to stop loading. At this point, the link will be loaded into tab 1 (incorrect behavior). This is enough to exhibit the tab state corruption bug, continue if you want to reproduce the crash. 6. Switch to the "Facebook" tab (tab 2). The page content will be the same as tab 1. Select the URL bar and hit enter - wait for the page to stop loading. 7. Switch to tab 1, which is now probably labeled "Facebook". Select the URL bar and hit enter - wait for the page to stop loading. 8. Switch to tab 3, which is probably still labeled "Comments". Select the URL bar and hit enter - wait for the page to stop loading. The browser will usually force-close at or before this point. 9. If the browser is still running, start at tab 1 and go through them selecting the URL bar and hitting enter. When getting to the Comments tab, click the link each time after reloading. This should work whether logged in to Facebook or not- if it doesn't work one way try logging in or out and retry.
Keywords: reproducible
The crash I see in the posted log is bug 707675.
This bug touches a lot of issues. Please file bugs for the individual issues so they can be tracked
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
The issue is that following the steps in comment 4 results in corruption of the browser's internal state as described in the original report. Data from one tab overwrites data in another in chaotic fashion. I'm not sure what you mean by "a lot of issues", there is only one here, which eventually results in a crash probably as a result of reading the corrupt data.
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: