Jeff Brown 4c05dd175e Ensure that viewport and frame are initialized. ... onInitializeDisplays() was posting a transaction with changes to the display projection. Unfortunately, it only set the display orientation field and left viewport and frame uninitialized. The uninitialized values flowed downstream and found themselves baked into a bogus DisplayDevice mGlobalTransform. That transform was then applied to some Rects which were turned into Regions that were them combined with other Regions. Under certain situations, the uninitialized data might have a largish value, resulting in the creation of Regions with components in excess of the Region max-value limit of 0x7ffffff (note that this is not INT_MAX). Later when performing a binary operation using the Region, the Spanner would loop indefinitely trying to figure out how to stuff a humongous region inside of a max-value region. Not content to try just once, the Spanner would continue trying again and again, pegging the CPU and hanging surface flinger during boot. Insanity soon followed. Bug: 7130713 Change-Id: I0016f0c9662185be833474c212a1dd408096ae23		2012-09-09 00:07:17 -07:00
..
powermanager	Use new PowerManager API.	2012-08-15 01:16:39 -07:00
sensorservice	add a way to enable debugging sensors at runtime	2012-06-28 19:46:54 -07:00
surfaceflinger	Ensure that viewport and frame are initialized.	2012-09-09 00:07:17 -07:00