Not sure if it is busy working in the background or has really started to ignore the screen but frequently I find that tapping the screen stops having any effect for a few seconds up to about 15 seconds.

Had this happen in the camera app, the screen kept being updated with the picture so I assume not too much is slowing things down. Same for dragging things around in the homescreen, the icons kept throbbing but touching the screen or home button did nothing.

In triage we decided to move this to general so that it goes through platform triage, is there a known bug with touchscreen drivers or similar? It could be that Gaia is just being unresponsive because the CPU is very busy but from the description it sounds like it could be something lower level.

Dave, is there a reliable set of steps one can use to reproduce this?

Nothing specific (aside from bug 803446), I just have to use the phone for a few minutes period of time and I usually hit it.

Dave Hylands said he could help investigate here. Without a reproducible test case it's hard to block on this since we don't know what the issue(s) is/are.

Actually, I just hazarded a guess that this was caused by the CPU being pegged at 100%, and that things will improve as we improve the overall performance of the system.

We discussed this again during triage today. Without a clear set of steps to reproduce, we can't block on it, sorry.

I started dogfooding yesterday and so far I've seen this happen probably 10 or 15 times. I've mostly noticed this when loading slashdot in the browser, zooming in so the article width fills the screen, then scrolling down as I read. I went to report this through the feedback app, and while I was typing up my comment there, the same thing happened, slashdot was still loaded in the background. Interestingly enough though, the cursor remained blinking in the feedback app, but the keyboard was not responding, nor was the home button. Based on what I've seen so far I think this is bad enough that we need to block on it whether we have STR or not. IMO this needs more eyeballs. After the 3rd time this happened in just mere minutes of using the phone it made me want to stop using the phone at all.

I agree, big-time qawanted. Oddly enough I never saw this in ~5 days of dogfooding :(.

Also, it seems the phone captures input during this time, i.e. if I'm trying to scroll while it's locked up, nothing happens, once it wakes up, it reacts to at least a good portion of the inputs I gave it. Still unclear on the details here though... Also, I don't know that this has anything to do with slashdot per se, that's just the site I used, and continued to use after I started seeing this.

I have occasional unresponsiveness STRs in this bug https://bugzilla.mozilla.org/show_bug.cgi?id=803430#c12

It hasn't really seemed to be a big annoyance in the 2012-10-18 build, but I might have bumped into this a few times in 2012-10-23 build, but I don't have reliable STR yet. and 2012-10-23 is also known to be more wonky than 2012-10-18 too.

Mossop, when this happens for you, are you able to open and close the "system tray"? (Drag down the bar at the top of the UI.) On the 10-24 stable build, I was able to reproduce something that seemed like bug 803430; homescreen was mostly unresponsive until I launched the settings app from the system tray. But the system tray stayed responsive the whole time.

Let's block on this but we may have to not do so if this turns out to just be that the phone's CPU is getting pegged and we can't do anything about it. cjones, who do you suggest owns this?

The phone's CPU isn't being pegged. Let's start by finding solid STR. That should give us an indication of where to look.

(In reply to Chris Jones [:cjones] [:warhammer] from comment #13) > Mossop, when this happens for you, are you able to open and close the > "system tray"? (Drag down the bar at the top of the UI.) > > On the 10-24 stable build, I was able to reproduce something that seemed > like bug 803430; homescreen was mostly unresponsive until I launched the > settings app from the system tray. But the system tray stayed responsive > the whole time. No, when this happens nothing responds until the phone starts working again.

OK. These may be separate bugs then.

Johnny says he hasn't seen this since getting the 2012-10-24 update. Mossop, are you still seeing this?

I think it might have reduced frequency since then, but I've still seen it as recently as yesterday

cjones, I'd love to give this to someone other than you but I can't think of anyone. Who would be a good owner?

We should see if this is still reproduced after bug 803430.

I can still repro this with screen defects of black screenshots occurring. also see : bug 807780

STR: 1. bring up browser app 2. hit home 3. hit contacts app 4. hit home 5. while starting the transition tap furiously on the screen.

STR: 1. bring up browser app 2. hit home 3. hit contacts app 4. hit home 5. while starting the transition tap furiously on the screen.

I was able to reproduce the same symptom as bug 803430 on latest-everything, but I still can't get the phone into a state where I can't pull down the system tray.

Filed bug 808157 for that. I'm easily able to reproduce the homescreen freeze, but I can't reproduce whole-screen freeze :(. nhirata, when you reproduce using STR in comment 24 are you still able to pull down the system tray?

(In reply to Naoki Hirata :nhirata from comment #22) > Created attachment 677597 [details] > screenshot > > I can still repro this with screen defects of black screenshots occurring. > > also see : bug 807780 That's bug 803447.

I can't reproduce this bug any more using the steps fom Comment 24 in the latest build. When the homescreen freezes in a prior version I could not pull down the system tray. cjones are you able to reproduce this bug with the latest build?

I've never been able to reproduce that symptom. I don't think this bug is serving a useful purpose anymore.