Natalya Kot [:nkot] Reporter
	Description • 11 years ago

Description:
 Scrolling functionality frequently freezes while in Settings. The issue is recoverable by killing the app and then relaunching, but since it happens quite often i thought it would better be investigated.

Repro Steps:
1) Updated Buri to BuildID: 20131120040202
2) Open Setting app
3) Scroll up/down

Actual:
 Unable to scroll, have to close app and relaunch to restore scrolling

Expected:
 Able to scroll every time when opening app

Environmental Variables:
Device: Buri v1.3 M-C 
BuildID: 20131120040202
Gaia: c26480b22ce28c812c347290dd4bad090d83db6f
Gecko: 4f993fa378eb
Version: 28.0a1
Firmware Version: V1.2_20131115

Notes:
the behavior also has been observed while in Terra app 

Repro frequency: 40%
See attached logcat, though I doubt there is anything in the logcat...

	Naoki Hirata :nhirata (please use needinfo instead of cc)
	Comment 1 • 11 years ago

within the logcat:
11-20 17:39:29.639: E/memalloc(136): /dev/pmem: No more pmem available
11-20 17:39:29.639: W/memalloc(136): Falling back to ashmem
11-20 17:39:29.699: E/msm7627a.hwcomposer(136): hwc_set: Unable to render by hwc due to non-pmem memory
11-20 17:39:29.709: D/HwcUtils(136): Skip layer

	Sotaro Ikeda [:sotaro]
	Comment 2 • 11 years ago

It might be great if we could have a video of the symptom. From Comment 1, it is not easy to understand the how ui was freezed.

	Sotaro Ikeda [:sotaro]
	Comment 3 • 11 years ago

It might be related to Bug 939348 and Bug 939565.

	Sotaro Ikeda [:sotaro]
	Comment 4 • 11 years ago

Bug 930926 might also be related.

	Natalya Kot [:nkot] Reporter
	Comment 5 • 11 years ago

this is a regression, the issue does not reproduce on yesterdays build:

BuildID: 20131119040204
Gaia: 4ecbc106a3fcf72cbd6dd8a43c46de7bacbedf20
Gecko: ba9ecdea3a90
Version: 28.0a1
Firmware Version: V1.2_20131115

Sotaro, 
i can record a video for you but actually it's just a screen that i cannot scroll :), open Settings app and cannot scroll up or down...

	Jason Smith [:jsmith]
	Comment 6 • 11 years ago

Does this reproduce on 1.2?

	Natalya Kot [:nkot] Reporter
	Comment 7 • 11 years ago

does not reproduce on 1.2

video of the issue - http://youtu.be/9bRtJxffeaY

	Naoki Hirata :nhirata (please use needinfo instead of cc)
	Comment 8 • 11 years ago

The video does see what I was seeing as well when I was doing some testing around this.  I think when : 
11-20 17:39:29.709: D/HwcUtils(136): Skip layer
occurs, you cannot pan.  I noticed quite a lot of the skip layer when looking at the logs and seeing this issue occur.

bug 907463 had landed within that regression window.  I am not sure if this is the cause of the issue as of yet.

	Walter Chen[:ypwalter][:wachen]
	Comment 10 • 11 years ago

It also reproduce in Nexus4, but it is not reproducible in Unagi.

Jason, I suggest that you can get some useful information then just comment or dup the bug. Also, read more before you dup/invalid a bug.

	Walter Chen[:ypwalter][:wachen]
	Comment 11 • 11 years ago

Also, additional information from bug 942701:

Enpei: First time boot is fine. second time boot, can't scroll.
Fugu and buri
Gaia:     087d109c83235fc157b2efac7ace6cc54a4c5aaa
Gecko:    8fdb69114734785065ce6c76ac36f4438b90c2e6
BuildID   20131127093419
Version   28.0a1

Also, might be bug 942259 related.

	Vivien Nicolas (:vingtetun) (:21) - (NOT reading bugmails, needinfo? please)
	Comment 12 • 11 years ago

I also explained in https://bugzilla.mozilla.org/show_bug.cgi?id=942701#c9

----
So it seems like the preallocated process is lying. The check at http://mxr.mozilla.org/mozilla-central/source/dom/browser-element/BrowserElementPanning.js#51 fails because the app says that docShell.asyncPanZoomEnabled == true while we are in the preallocated process.

When the prealocatted process is consume by a real app, this value is correct but it is too late.

I seems like something has changed in the way we initialize the asyncPanZoomEnabled value by default.

----


I'm not sure this is the issue here, but since the other bug has been resolved as a duplicate of this one.

	Preeti Raghunath(:Preeti)
	Comment 13 • 11 years ago

Kevin
Please check if this feature of DSDS is supported for 1.3.

	Jason Smith [:jsmith]
	Comment 14 • 11 years ago

(In reply to Preeti Raghunath(:Preeti) from comment #13)
> Kevin
> Please check if this feature of DSDS is supported for 1.3.

This isn't related to DSDS. It's just a plain settings app gecko regression.

	Kai-Chih Hu [:khu]
	Comment 15 • 11 years ago

Just like what Jason said. Actually, I don't think it's related to DSDS...

	Milan Sreckovic [:milan] (needinfo for best results)
	Comment 16 • 11 years ago

I see Jason asking for a regression range, is the regression range in comment 5 valid?

	Jason Smith [:jsmith]
	Comment 17 • 11 years ago

(In reply to Milan Sreckovic [:milan] from comment #16)
> I see Jason asking for a regression range, is the regression range in
> comment 5 valid?

Oh - missed that. Clearing regression window wanted then.

	Milan Sreckovic [:milan] (needinfo for best results)
	Comment 18 • 11 years ago

Is this any better when APZC is enabled (in the systems menu) and phone restarted?

	Natalya Kot [:nkot] Reporter
	Comment 19 • 11 years ago

It seems to be better now, I haven't seen this scrolling issues lately

	Jason Smith [:jsmith]
	Comment 20 • 11 years ago

(In reply to Natalya Kot [:nkot] from comment #19)
> It seems to be better now, I haven't seen this scrolling issues lately

So can we close this as works for me then?

	Natalya Kot [:nkot] Reporter
	Comment 21 • 11 years ago

(In reply to Jason Smith [:jsmith] from comment #20)

> So can we close this as works for me then?

I would say so.
I've also asked testers around, the issue no longer happens to us (we have 20 testers in the room :)), so can be closed.