Skip to content
Snippets Groups Projects
Select Git revision
  • eec5e52ea24a9b86a9cee75c1e3207e9378b41c8
  • master default protected
  • android-7.1.2_r28_klist
  • oreo-mr1-iot-release
  • sdk-release
  • pie-cts-dev
  • pie-cts-release
  • pie-vts-release
  • nougat-iot-release
  • pie-gsi
  • pie-platform-release
  • pie-r2-release
  • pie-r2-s1-release
  • pie-release
  • pie-dev
  • oreo-m4-s4-release
  • o-mr1-iot-preview-8
  • oreo-m2-s2-release
  • oreo-m2-s1-release
  • oreo-m6-s2-release
  • oreo-m6-s3-release
  • android-o-mr1-iot-release-1.0.4
  • android-9.0.0_r8
  • android-9.0.0_r7
  • android-9.0.0_r6
  • android-9.0.0_r5
  • android-8.1.0_r46
  • android-8.1.0_r45
  • android-n-iot-release-smart-display-r2
  • android-vts-8.1_r5
  • android-cts-8.1_r8
  • android-cts-8.0_r12
  • android-cts-7.1_r20
  • android-cts-7.0_r24
  • android-cts-6.0_r31
  • android-o-mr1-iot-release-1.0.3
  • android-cts-9.0_r1
  • android-8.1.0_r43
  • android-8.1.0_r42
  • android-n-iot-release-smart-display
  • android-p-preview-5
41 results

libutils

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Hans Boehm authored
    The compensating onLastStrongRef call could be made even when there
    was no onIncStrongAttempted call to compensate for.  This
    happened in the OBJECT_LIFETIME_STRONG case when e.g. curCount
    was initially zero, but was concurrently incremented by another
    thread.
    
    I believe the old code was also incorrect in the
    curCount = INITIAL_STRONG_VALUE + 1 case,
    which seems to be possible under unlikely conditions.
    In that case, I believe the compensating call IS needed.
    Thus the condition was also changed.
    
    Clean cherrypick of 7f27cbc3 from AOSP.
    
    Bug: 30503444
    Change-Id: I44bcbcbb1264e4b52b6d3750dc39b041c4140381
    1b07c95b
    History
    Name Last commit Last update
    ..