| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
bug:7266561
this makes them safe for cross-thread usage
Change-Id: Ib3a49999aa5c3e740127ba684f3d4887e1ad5cb9
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
bug:7271856
Path was untested/broken
Change-Id: I053cb0255665b57b89524debbad9f78286ba9a37
|
|\ \
| | |
| | |
| | | |
computation" into jb-mr1-dev
|
| |/
| |
| |
| |
| | |
bug:7267294
Change-Id: Ia6de9264b6c3680707b8fb8833d69d7cc7e850e8
|
|/
|
|
|
|
| |
bug:7247750
Change-Id: I8238acc2c20942ab2f42936d16a03226909aebcd
|
|
|
|
|
| |
bug:7247486
Change-Id: Iba6b37d50985b51585e6e96a35705da54aae9878
|
|
|
|
|
| |
bug:7188900
Change-Id: I9cfc020be463b0441a3d718d44cc6c948781d7cf
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Bug: 7163457
Oops
Change-Id: I08d25259810faa3983e6f84165b5ae9f286ece3f
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
Bug: 6937596
Change-Id: I451e8c10eb2b3e5c2a8f46d3e7b278fa5810d27e
|
|\ \
| | |
| | |
| | | |
jb-mr1-dev
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug: 7073422
Use a flag and annotation for allowing access to inherited methods of
jsinterface objects. When flag is false, no annotation is needed. When
flag is true, annotation is needed for allowing access to inherited methods.
Change-Id: I610119dc5410d8df1962fa9dbea09866f81d374c
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| | |
bug:7128794
Change-Id: Id36dbedcb7c8245fc6f37dbf938b085da3e0ae93
|
|/
|
|
|
|
|
|
|
|
| |
Bug: 7089191
SVGImage is created with an EmptyFrameLoaderClient. This client
returns a null networkingContext(), which will than cause
ResourceHandleAndroid to crash. The fix is simple, return a load
failure if we are given a null or invalid NetworkingContext
Change-Id: Ib25c2449527ca7d3693b78425c0bc5f2e9a12f74
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Bug: 7082715
Also fixes the glitch with drawing a disabled select leaving
an alpha set on the context
Change-Id: I8414ca4332f4828453e4f5b1e9186b13d319dfbb
|
|\ \
| |/
|/|
| |
| |
| |
| | |
writing/reading"
* commit '43e94fa8daa7eaaece0da98e14809891b3fd2b4c':
Remove inconsistency between HistoryItem writing/reading
|
| |\
| | |
| | |
| | |
| | | |
* commit '1a6030e76fa5fa0c0a19aeb7d7a53070b9438ea6':
Remove inconsistency between HistoryItem writing/reading
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes inconsistent writing of HistoryItem formData
for the case when formData is not null,
but it gets flattened and saved as empty string.
FormData identifier also gets written in that case,
which creates problem on HistoryItem reading,
when parser does not expect to meet form identifier
after it reads zero as FormData size.
Change-Id: I77cf00b5b2a0f2a7cf4355d1bc1b8d4830ac1afb
|
|\ \ \
| | | |
| | | |
| | | | |
jb-mr1-dev
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The function isn't threadsafe, so races would occur and certain textures
wouldn't be removed from ImagesManager's master list. The list would then be
iterated over, all items dereferenced, and bad times would ensue.
The SkRefCnt class uses atomic inc/dec to decide when to destroy an object, but
reading such an integer non-atomically isn't safe. Instead use the real signal
we're looking for - when the ImageTexture is deleted - to know when to remove
the ImageTexture from ImagesManager's list.
Mutual exclusion from editing the list is now maintained by only unref-ing the
ImageTexture within releaseImage, which holds the ImagesManager's m_imagesLock
(which we already do anyway).
bug:6859278
Change-Id: I75ebf79f2617484e7df355d6539226ce64882369
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 7074134
There are early returns in the TextIterator ctor that would result
in m_needsAnotherNewline being left unitialized. This results in
the first call to advance() crashing due to m_needsAnotherNewline
taking an earlier path that doesn't have all the same initialized
checks
Change-Id: I1d89912532275323f71de8055c33257619b93cbb
|
|\ \ \ \ |
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The flush() method of the cookie jar can be accessed from different
threads. This method (eventually) creates a NewRunnableTask and a
callback on FlushSemaphore object. Therefore FlushSemaphore should
inherit from a ThreadSafe ref counter rather than a simple base ref
counter.
Change-Id: Ie6914fba9b1554081c4b3b5992661af066e23653
|
|\ \ \ \
| |/ / /
|/| / /
| |/ /
| | | |
* commit '4d33d9fbe70f0b56bd2c9bf8e6269ae21b4a5521':
Crash on Orange media portal
|
| |\ \
| | |/
| | |
| | |
| | | |
* commit '5fe0a0bed6096da8fb7beef2708c36972d67b723':
Crash on Orange media portal
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Visit orange.deezer.com, press tab marked "My Music".
Browser crashes every time.
Pressing the button will trigger a re-layout of the page.
This in turn will cause some rendering nodes of type
RenderLayer to be removed from the rendering tree.
When such a node is removed, it is important to also
update certain lists in ancestor nodes that may hold references
to this node. A node that may hold such a reference is
identified as being a "stacking context".
However, in Android, when the symbol ENABLE_COMPOSITED_FIXED_ELEMENTS
is defined, the definition of what is a stacking context
is expanded. In this case, a node that is a stacking context
and holds references to descendants, changes one of the conditions
that form part of Android's expanded stacking context definition.
So, now it is no longer a stacking context, but the reference list
is not deleted/updated. When the descendant node is removed a
search for an ancestral stacking context is made, but it will
not find this node since it is no longer a stacking context.
The solution is to make sure that the list of references is
updated/cleared whenever the node changes a condition that
may cause its status as a stacking context to also change.
Change-Id: If5a7b63715020bc3d23749a7c09003a86d90e28d
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 6662557
Provide the plumbing for passing referer for downloads.
Change-Id: Ia4af34632be5e5df44b7d19501db1b589c45cddf
|
|\ \ \ \
| |/ / /
|/| / /
| |/ /
| | | |
* commit 'f2b8b88d1a8fefaf6de6c6bce24ae092abdf9584':
Fix memory leak caused by CSSRuleList wrapper
|
| |\ \
| | |/
| | |
| | |
| | | |
* commit '5161915319ca55318d2ef68a84b735f01c3d202f':
Fix memory leak caused by CSSRuleList wrapper
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Accessing cssrulelist in javascript will create a new
CSSRuleList object and wrapper JS object. The wrapper
JS object will be added into hidden array in parent JS
object which is alive during the whole execution. Thus
memory leak happens (CSSRuleList in webkit, wrapper object
and weak global handle in v8).
Cherry pick 2 patches from upstream solves the problem:
http://trac.webkit.org/changeset/90949
This patch changes hidden reference from array to named
property. So new wrapper will replace old wrappper. But the
memory leak still exists because the CSSRuleList wrapper
will be added into an object group of current document. So
they will still be alive during execution.
http://trac.webkit.org/changeset/91256
This patch avoids to adding CSSRuleList wrapper into document
object group. Combined with the first patch, it can resolve
the memory leak problem.
Change-Id: Icb523db52963726f27b6c02596822cfb6e8d5049
Author: Vitaly Repeshko <vitalyr@chromium.org>
Signed-off-by: Xi Qian <xi.qian@intel.com>
Signed-off-by: Shuo Gao <shuo.gao@intel.com>
Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>
Signed-off-by: Jack Ren <jack.ren@intel.com>
Author-tracking-BZ: 32630
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
* commit '465864a6d72a2505b7a725ddaadfff05cdece8fc':
DO NOT MERGE Null check
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Cherry pick
Bug: 6975836
Fixes a crash in find on page
Change-Id: I20e1597f2f3a381ee693c1bcef944243ca654110
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | | |
* commit '28c43cfac56492d4d307386c44ab9a1121f7d3bf':
DO NOT MERGE Fix memory leak
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Cherry pick
Bug: 6952980
GraphicsContext::createOffscreenContext creates an instance of both
PlatformGraphicsSkia and GraphicsContext for ImageBuffer. However,
ImageBuffer will only call delete on the GraphicsContext. In normal
GC usage, the PlatformGraphicsContext's lifecycle is longer than the
GCs, and is cleaned up by itself. This will result in leaking the
PlatformGraphicsSkia context, though. We need to make sure to call
delete on the PlatformGraphicsSkia context if we were initialized
with the deleteUs() flag, which is used to indicate just this scenario.
Change-Id: If908dcb44e99568b92ee63d6337ce9f84adc9adf
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I807620f965779274e36aac6729dc1e6374ff8716
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
into jb-mr1-dev
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Bug 7025068
When the input field is empty, the selection was appearing outside
the input field. With this change, we fall back to the caret rect
for the text around the caret.
Change-Id: Ie6122ec34a0ae96994dc91b002bdcb3403b753eb
|
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Avoids region & matrix computation work for small ops. Area value of 750
determined empirically.
Change-Id: Iffc041ff69cd47c152ae4f71a474f4f6ccdc0bc5
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
bug:6389297
This improves performance in capturePicture, since it avoids all of the clipping
and opaque region tracking logic.
Change-Id: If1db553b2568573f94cdee7b801c67be0c47c056
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
into jb-mr1-dev
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
bug:7002755
This prevents the SurfaceCollectionManager from getting stuck in fast swap mode,
where because swaps are occuring in process mode, and not in draw mode, which
would previously have prevented the flag from being cleared.
Change-Id: Ie888438c73aabeeff0534caad68b58e4acd2c440
|
|\ \ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Cherry-pick I2a69f2834ca50c37302dcd4816edb630b1208a41 from master.
This change allows WebView to continue to function as before,
displaying text using the system default fallback font chain.
Change-Id: Ibcb8924d270cc602295158684bd700cfcbb1ec46
|