Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.platforms.mobile
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
StrictMode's red screen flashing enabled
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Chris Peterson  
View profile  
 More options Aug 13 2012, 11:17 am
Newsgroups: mozilla.dev.platforms.mobile
From: Chris Peterson <cpeter...@mozilla.com>
Date: Mon, 13 Aug 2012 11:17:33 -0400
Local: Mon, Aug 13 2012 11:17 am
Subject: StrictMode's red screen flashing enabled
Print | Individual message | Show original | Report this message | Find messages by this author
I just landed bug 781274 that will opt into Android's Strict Mode
"screen flashing". This testing feature displays a red border when
Fennec calls Android APIs on the UI thread that can cause long UI delays
(such as file or network I/O).

Here is a screenshot of StrictMode's red border:
https://bug782263.bugzilla.mozilla.org/attachment.cgi?id=651366

This only affects "unoffical" builds (local, Nightly, and Aurora
channels) running on Android >= Honeycomb.

The red borders will probably be intermittent, but they should be filed
as UI bugs. Fennec will dump useful debug info to logcat after flashing
the screen.

If the red borders are causing excessive failures of automated UI tests
or people think they are inappropriately aggressive, then I can disable
them.

chris p


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Chris Peterson  
View profile  
 More options Aug 13 2012, 11:32 am
Newsgroups: mozilla.dev.platforms.mobile
From: Chris Peterson <cpeter...@mozilla.com>
Date: Mon, 13 Aug 2012 11:32:05 -0400
Local: Mon, Aug 13 2012 11:32 am
Subject: Re: StrictMode's red screen flashing enabled
Print | Individual message | Show original | Report this message | Find messages by this author
I should note that we've had StrictMode logcat reporting for months. I
enabled the red screen flashing in response to QA and SUMO discussions
about how to get more info about ANR errors in the field.

StrictMode screen flashing will let our (Nightly and Aurora) users tell
us whether the ANR was related to some slow code we called on our UI
thread or some other issue.

chris


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google