- 08 Jan, 2014 40 commits
-
-
mlamouri@chromium.org authored
BUG=None Review URL: https://codereview.chromium.org/121673004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243554 0039d316-1c4b-4281-b951-d872f2087c98
-
thestig@chromium.org authored
NOTRY=true TBR=thakis@chromium.org BUG=162825,293049,332271,332328,332329,332330,332335 Review URL: https://codereview.chromium.org/127933002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243553 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243552 0039d316-1c4b-4281-b951-d872f2087c98
-
eseidel@chromium.org authored
http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=164656:164662&mode=html TBR= BUG= Review URL: https://codereview.chromium.org/127913002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243551 0039d316-1c4b-4281-b951-d872f2087c98
-
kinaba@chromium.org authored
Actual implementation will come later. This CL just addes the interface. BUG=324166 Review URL: https://codereview.chromium.org/127463004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243550 0039d316-1c4b-4281-b951-d872f2087c98
-
tfarina@chromium.org authored
BUG=None TEST=checkdeps passes TBR=ben@chromium.org Review URL: https://codereview.chromium.org/126893003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243549 0039d316-1c4b-4281-b951-d872f2087c98
-
djkurtz@chromium.org authored
Most X DRI2 drivers return TRUE for GetSyncValues with a MSC value of 0 if they cannot deduce on which CRTC the Drawable is being displayed, or that CRTC is currently disabled. This can happen if the associated CRTC is powered off, or if its framebuffer is being rotated, etc. Once the driver is in this situation, all MSC == 0 values will be returned until the CRTC can be found again. Currently, we spam the log every time we receive msc==0, which fills up the disk, makes the GPU log unusable, and causes lots of confusion when devs are trying to debug other issues. Instead, let's just log exactly once every time this situation is detected. Signed-off-by:
Daniel Kurtz <djkurtz@chromium.org> BUG=231945 TEST=Manual on chromeos: # Enable some slowly updating page on each monitor, for example: http://www.24webclock.com/ tail -F /var/log/chrome/chrome | grep glXGetSyncValuesOML & set_short_timeouts # Let the displays turn off (~35 seconds) => This message should be printed exactly once per attached display: glXGetSyncValuesOML should not return TRUE with a media stream counter of 0. # Turn displays back on (tap a key), and let them idle off again. => The same message should be printed exactly once per attached display. R=marcheu@chromium.org R=piman@chromium.org R=backer@chromium.org Review URL: https://codereview.chromium.org/126823006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243548 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243547 0039d316-1c4b-4281-b951-d872f2087c98
-
robertphillips@google.com authored
R=rmistry@google.com Review URL: https://codereview.chromium.org/110413009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243546 0039d316-1c4b-4281-b951-d872f2087c98
-
ernstm@chromium.org authored
This CL causes Chrome to freeze on e.g. jsfiddle.net/r8dx9/1/embedded/result See crbug.com/331534 for details. > cc: Simplify raster task completion notification logic > > Previously the pixel buffer raster worker pool used a combination of > polling and explicit notifications from the raster worker pool to decide > when to tell the client about the completion of 1) all tasks or 2) the > subset of tasks required for activation. This patch simplifies the logic > by only triggering the notification based on the OnRasterTasksFinished > and OnRasterTasksRequiredForActivationFinished calls from the worker > pool. > > BUG=307841 > > Review URL: https://codereview.chromium.org/99873007 R=reveman@chromium.org,skyostil@chromium.org BUG=331534 Review URL: https://codereview.chromium.org/126143006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243545 0039d316-1c4b-4281-b951-d872f2087c98
-
dconnelly@chromium.org authored
This one got left out of the mass icon switch. BUG=323658 Review URL: https://codereview.chromium.org/125853003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243544 0039d316-1c4b-4281-b951-d872f2087c98
-
jeremy@chromium.org authored
Needed for theme and many extension startup tests. * Add benchmarks/startup_with_extensions.py - new theme and many_profile startup tests. * Teach test.py to use .sha1 files for profile directories, these are downloaded from cloud storage, unzipped and then used as the profile directory by the browser. * Add a function to browser_finder to allow querying the target OS. BUG=None Review URL: https://codereview.chromium.org/124733002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243543 0039d316-1c4b-4281-b951-d872f2087c98
-
navabi@google.com authored
Rebooting s3 devices causes device to be flaky during the deploy step. This is likely because WaitForPackageManager() does not wait long enough on the s3 devices. I've verified locally on the bot that without the reboot in the provision step, the devices are more reliable (i.e. deploy step passes). BUG=321063 TBR=frankf@chromium.org Review URL: https://codereview.chromium.org/122313008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243542 0039d316-1c4b-4281-b951-d872f2087c98
-
isherman@chromium.org authored
Also, re-arrange a bit of code in the implementation file for slightly clearer structuring. BUG=none TEST=none R=estade@chromium.org TBR=joi@chromium.org,zea@chromium.org Review URL: https://codereview.chromium.org/122313007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243541 0039d316-1c4b-4281-b951-d872f2087c98
-
hclam@chromium.org authored
Adding parameters to Cast Streaming Extensions API to configure AES encryption key and IV mask to CastSender. BUG=315931 Review URL: https://codereview.chromium.org/121543003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243540 0039d316-1c4b-4281-b951-d872f2087c98
-
hashimoto@chromium.org authored
Keep resource ID of these entries empty. Remove IsSpecialResourceID(). BUG=324717 TEST=unit_tests Review URL: https://codereview.chromium.org/118953003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243539 0039d316-1c4b-4281-b951-d872f2087c98
-
mtomasz@chromium.org authored
When opened selected a USB volume in Files app, and crashed, the Files app is tried to be restored with the previous path. However, the volume may not yet be available. In such case, parent is considered. However, parent is /removable, which resolving causes an error, resulting in throwing an exception and going into a wrong state. In such situation, we should fallback, and this is what this patch does. If the parent is not resolvable, then the fallback is used as the next current directory instead. Moreover, after recent refactoring a regression has been introduced. When resolving a parent of the initial directory fails, then a wrong variable name was used, what caused a JS error. TEST=Tested manually on Pixel. BUG=331587 Review URL: https://codereview.chromium.org/124933002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243538 0039d316-1c4b-4281-b951-d872f2087c98
-
mnaganov@chromium.org authored
First, turning on JS, which is disabled by default. Also, no one guarantees that onload + writeln + onPageFinished must work as you'd expect, so there is no point in testing this scenario. So just change this test to verify that the title updated via JS is reported by GetTitle. BUG=151012 Review URL: https://codereview.chromium.org/117993005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243537 0039d316-1c4b-4281-b951-d872f2087c98
-
mgiuca@chromium.org authored
This avoids showing a double title bar on browser windows without a tab strip, such as popups, Developer Tools and V1 app windows. BUG=330090 TEST=On Unity, maximize Developer Tools window. There should be only the Unity title and caption buttons, no blue custom title bar. Review URL: https://codereview.chromium.org/117233008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243536 0039d316-1c4b-4281-b951-d872f2087c98
-
eranm@google.com authored
No functional changes. BUG=309578 Review URL: https://codereview.chromium.org/115013004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243535 0039d316-1c4b-4281-b951-d872f2087c98
-
yukishiino@chromium.org authored
This CL addresses the remaining comments at http://crrev.com/121183002 . TEST=none Review URL: https://codereview.chromium.org/114033005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243534 0039d316-1c4b-4281-b951-d872f2087c98
-
qsr@chromium.org authored
Page.disable clears all scripts to evaluate on commit. There is no way to detect client side redirects because linkedin, for example, performs its client side redirect after the page has fully loaded. In order for the page_cyclers to work on pages with client side redirects, the script to evaluate on commit must execute on the redirected page. So to workaround this, we avoid ever calling Page.disable. we don't expect continuing to listen for notifications here to impact performance, but if we do see any performance reduction on the bots we should revert and search for another approach. This is a reland of https://codereview.chromium.org/103373003 fixing failures on the bots. BUG=253604 R=pdr@chromium.org TEST=tools/perf/run_measurement --browser=canary page_cycler tools/perf/page_sets/top_10_mobile.json --pageset-repeat=2 Review URL: https://codereview.chromium.org/112413006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243533 0039d316-1c4b-4281-b951-d872f2087c98
-
reveman@chromium.org authored
This adds a DiscardableMemoryType enum and a function that can be used to select what type of discardable memory to use. This is generally useful for debugging purposes and when evaluating the performance of one implementation vs another. The unit test framework for discardable memory is improved slightly by testing every supported type on each platform rather then just the one specific type. Furthermore, it allows us to expose ashmem based discardable memory on ChromeOS in about:flags before we make it default. No change in behavior unless the new --use-discardable-memory=type switch is used. BUG=327516 TEST=base_unitttest --gtest_filter=DiscardableMemory* TBR=tomhudson@google.com Review URL: https://codereview.chromium.org/114923005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243532 0039d316-1c4b-4281-b951-d872f2087c98
-
hashimoto@chromium.org authored
To fix use-after-free BUG=331822 TEST=See no crash after following the repro steps described in the BUG. Review URL: https://codereview.chromium.org/127613002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243531 0039d316-1c4b-4281-b951-d872f2087c98
-
binjin@chromium.org authored
Implements ash::internal::LogoutConfirmationDialogView which is supposed to be used by ash::internal::LogoutButtonTray. BUG=223846 TEST=new unit test Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=242286 Review URL: https://codereview.chromium.org/40053002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243530 0039d316-1c4b-4281-b951-d872f2087c98
-
dconnelly@chromium.org authored
The old approach chose the nav dot width by measuring a phantom dot containing the string "Most Visited," but only when the Most Visited dot is shown. This approach fails when it isn't shown, or when the string "Apps" is longer than the string "Most Visited" in the user's local language. Screenshots on the bug. BUG=248495 Review URL: https://codereview.chromium.org/110523004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243529 0039d316-1c4b-4281-b951-d872f2087c98
-
haraken@chromium.org authored
Trace-viewer side change is here: https://codereview.appspot.com/39310043 Screenshot of the profiler: http://haraken.info/null/sampling_tracing.png Design document: https://docs.google.com/a/google.com/document/d/1j39sbA9ECTwFFlxbhSD1EvJnGfYeS5EUJ05yxuku6VY/edit TBR=phajdan.jr NOTRY=true Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=242671 Review URL: https://codereview.chromium.org/109933006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243528 0039d316-1c4b-4281-b951-d872f2087c98
-
skuhne@chromium.org authored
Finally - the first two functions which go for good! BUG=322682 TEST=covered by other unit tests Review URL: https://codereview.chromium.org/109823010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243527 0039d316-1c4b-4281-b951-d872f2087c98
-
yoshiki@chromium.org authored
BUG=223574 TEST=manually tested Review URL: https://codereview.chromium.org/108163005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243526 0039d316-1c4b-4281-b951-d872f2087c98
-
hirono@chromium.org authored
Event names and dictionary values in the event router of Files.app can be replaced with constants and types generated by the IDL compiler. BUG=330638 TEST=none Review URL: https://codereview.chromium.org/107813005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243525 0039d316-1c4b-4281-b951-d872f2087c98
-
jadahl@opera.com authored
Add support for having multiple queries to be active at the same time given that their targets are different. BUG=328808 Review URL: https://codereview.chromium.org/106623008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243524 0039d316-1c4b-4281-b951-d872f2087c98
-
tzik@chromium.org authored
* Move shared constants between V1 and V2 to drive_backend_constants. * Drop dependency from FakeDriveServiceHelper to APIUtil BUG=331991 Review URL: https://codereview.chromium.org/103013003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243523 0039d316-1c4b-4281-b951-d872f2087c98
-
taken.spc@gmail.com authored
for assistive technologies on Windows. This changeset adds support for - article (xml-roles:article) - header (xml-roles:banner) - aside (xml-roles:complementary) - address (xml-roles:contentinfo) - footer (xml-roles:contentinfo) - main (xml-roles:main) - nav (xml-roles:navigation) - section (xml-roles:region) Patch from Takeshi Kurosawa <taken.spc@gmail.com> BUG=253027 TEST=content\renderer\accessibility\accessibility_node_serializer.cc Review URL: https://codereview.chromium.org/98183011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243522 0039d316-1c4b-4281-b951-d872f2087c98
-
jochen@chromium.org authored
BUG=332341 TBR=ccameron@chromium.org Review URL: https://codereview.chromium.org/127753003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243519 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243517 0039d316-1c4b-4281-b951-d872f2087c98
-
machenbach@chromium.org authored
R=engedy@chromium.org TBR=verwaest@chromium.org Review URL: https://codereview.chromium.org/123423003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243516 0039d316-1c4b-4281-b951-d872f2087c98
-
jochen@chromium.org authored
BUG=332331 TBR=bbudge@chromium.org Review URL: https://codereview.chromium.org/127813002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243515 0039d316-1c4b-4281-b951-d872f2087c98
-
yoshiki@chromium.org authored
This patch is a revert of r234889 "[Files.app] Show files beginning with '.' (dot)", which causes Issue 330513. BUG=196539, 330513 > [Files.app] Show files beginning with '.' (dot) > > BUG=196539 > TEST=manually tested > R=hirono@chromium.org > > Review URL: https://codereview.chromium.org/71503003 TBR=yoshiki@chromium.org Review URL: https://codereview.chromium.org/127803002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243514 0039d316-1c4b-4281-b951-d872f2087c98
-
chrome-admin@google.com authored
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243513 0039d316-1c4b-4281-b951-d872f2087c98
-
jochen@chromium.org authored
http://build.chromium.org/f/chromium/perf/dashboard/ui/changelog_blink.html?url=/trunk&range=164506:164655&mode=html TBR= BUG= Review URL: https://codereview.chromium.org/127673002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@243512 0039d316-1c4b-4281-b951-d872f2087c98
-