Skip to content
Snippets Groups Projects
Select Git revision
  • test default
1 result
Search by author
  • Any Author
  • Admin, Lime Admin, Lime lime_admin
  • CodeLinaro CodeLinaro codelinaro
  • CodeLinaro Hoperun CodeLinaro Hoperun hoperun
  • Joshua S. (Stage) Joshua S. (Stage) joshua.sickmeyer
  • Park, Jae Woo Park, Jae Woo jaewpark
5 authors
  1. Jun 14, 2019
  3. May 23, 2019
  5. May 10, 2019
  7. May 07, 2019
  9. May 02, 2019
    • Valerie Hau's avatar
      Modify gralloc0 implementation · 9b04e0a9
      Valerie Hau authored 
      Add validateBufferSize and getTransportSize

Bug: 131089111
Test: build, boot
Change-Id: I052f9537fa1b37a4a7b2f5d82309aff3d2e1f2f3
      9b04e0a9
  11. Mar 12, 2019
  13. Mar 07, 2019
  15. Feb 25, 2019
  17. Feb 24, 2019
  19. Feb 21, 2019
  21. Jan 06, 2019
  23. Dec 17, 2018
  25. Dec 15, 2018
  27. Nov 28, 2018
  29. Nov 27, 2018
  31. Nov 26, 2018
  33. Nov 20, 2018
  35. Nov 19, 2018
  37. Nov 04, 2018
  39. Nov 02, 2018
  41. Nov 01, 2018
    • TreeHugger Robot's avatar
      Merge "Silence a static analyzer warning" · 0af0a2c5
      TreeHugger Robot authored
      0af0a2c5
    • George Burgess IV's avatar
      Silence a static analyzer warning · d2b525e7
      George Burgess IV authored 
      Our static analyzer is unhappy with this code, and thinks it has a
memory leak:

device/generic/opengl-transport/host/libs/virglrenderer/AVDVirglRenderer.cpp:343:38:
warning: Potential leak of memory pointed to by 'config'
[clang-analyzer-cplusplus.NewDeleteLeaks]

While this immediately seems true, the constructor for `config` will
stash a pointer to `config` in a static vector, which presumably is
meant to manage the lifetime of our newly-allocated `config`.

As noted in the comments, the analyzer can generally reason about that,
but it gives up trying to figure out what the constructor is doing
before we reach the vector's push_back.

Just put a NOLINT here to make it be quiet.

Bug: None
Test: Ran the analyzer. It's no longer angry.
Change-Id: Ida0118ef8b9ca0cd40cdd5e76489ab14cb86ea23
      d2b525e7
  43. Oct 31, 2018
  45. Oct 30, 2018
  47. Oct 29, 2018
  49. Oct 27, 2018
  51. Oct 26, 2018
  53. Oct 25, 2018
  55. Oct 24, 2018