Created attachment 711010 [details]
Screenshot of issue
1. Go into maps
2. App eventually launches
3. Suddenly I get the attached screenshot. All UI on all screens is missing - rebooting the phone fixes the issue.
I'm unable to reproduce this.
Marcia, can you reproduce this on a more recent build? I haven't had issues using maps.
Dave Hunt, I believe, has seen this too, as have I (with different apps/scenarios, though, I think); trying to reproduce and capture it in a logcat.
I haven't seen this again yet using:
But would like to spend some time since I got this build late yesterday.
Stephen: Have you seen this on unagi or inari?
(In reply to Marcia Knous [:marcia] from comment #4)
> Stephen: Have you seen this on unagi or inari?
Unagi, with our engineering builds (and I think both manually/through automation, but primarily through automation?)
Unfortunately this happened again to me tonight during testing using the new build I just pulled down this afternoon on Inari.
This is what shows from checkversion:
The last thing I was doing before this happened - I had the app Pulse open and I hit the Home button. After that all the UI on the homescreens is blank, and I had to reboot the phone to get back to a good working state.
(In reply to Marcia Knous [:marcia] from comment #6)
> Unfortunately this happened again to me tonight during testing using the new
> build I just pulled down this afternoon on Inari.
> This is what shows from checkversion:
> Gaia eec503b364ecb17200cf87487be9f0d96b6fcbe8
> BuildID 20130208144804
> Version 18.0
> The last thing I was doing before this happened - I had the app Pulse open
> and I hit the Home button. After that all the UI on the homescreens is
> blank, and I had to reboot the phone to get back to a good working state.
Even using cards view to switch to another app?
(In reply to Alive Kuo [:alive](on Chinese New Year: 2/7~2/17) from comment #7)
good working state.
> Even using cards view to switch to another app?
Yes - all that shows in the UI is what I have in the attached screenshot - nothing shows on the screen, you cannot advance to any of the other screens - none of the apps shows so there is no way to switch to another app and pressing the Home button does nothing. Rebooting the phone is the only way to solve it, and you are able to get the restart UI by holding down the power button and selecting restart.
I am also able in this state to get the lock screen up, and I was able to switch to camera briefly, but when I came back from the unlock screen the homescreen still looked like what I have shown in the screenshot.
I have now seen this testing on the BeetleLite device today as well, using:
On this device I was able to get the card view to show, but I cannot drag the cards up or use the "x" to close them. I am basically stuck in card view.
This sounds like a general gecko/gaia issue.
Better STR would help a lot - I poked around trying to make the device run out of memory but I couldn't reproduce this. Also, the output of logcat and b2g-ps after this happens could help us figure out what's going on.
I have seen something similar when running the Gaia UI tests.. mid-way through the suite the home screen appears as it does in attachment 711010 [details]. This causes certain tests that interact with the home screen to fail. Unfortunately I do not currently have a reduced test case.
Note that in comment 11 I am seeing this on an Unagi using an eng build.
I saw this last night on unagi as well using the latest nightly build - I will try to get you better STR but at the time I did not have phone connected to logcat.
The occurrence last night was after a bluetooth file transfer. On unagi I was able to recover by pressing the power button and then refreshing the phone. I was not able to do that on the other two phones when it occurred.
I finally reproduced this. There is no homescreen process after this happens - just the last app I was using. The only hints I see are lines in logcat complaining about running out of pmem and some gonkmemorypressure messages. There is also no preloaded plugin-container in sight.
There's an existing bug that's mostly fixed by bug 836654 where if an app crashes before we load its BrowserElementParent, we don't send a mozbrowsercrash event to the embedder, so it never discovers that the frame crashed. Perhaps that's what's going on here.
Is anyone still reproducing this?
I personally haven't seen it during device testing recently. I'll let Dave Hunt and others comment as to their experience seeing it.
(In reply to Chris Jones [:cjones] [:warhammer] from comment #16)
> Is anyone still reproducing this?
I'm going to go ahead and close out then, since there's not a lot more we can usefully do with this bug. If it reappears, let's file a new one.