mirrored from https://chromium.googlesource.com/webm/libvpx
-
Notifications
You must be signed in to change notification settings - Fork 348
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: webmproject/libvpx
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.13.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: webmproject/libvpx
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.13.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 7 commits
- 8 files changed
- 2 contributors
Commits on Feb 13, 2023
-
README: update release version to 1.13.0
this was missed in the v1.13.0 tag Bug: webm:1780 Change-Id: I3044534123bf67861174970e6241f6586055358e (cherry picked from commit 184a886)
Configuration menu - View commit details
-
Copy full SHA for b5e1945 - Browse repository at this point
Copy the full SHA b5e1945View commit details
Commits on Sep 27, 2023
-
encode_api_test: add ConfigResizeChangeThreadCount
Update thread counts and resolution to ensure allocations are updated correctly. VP8 is disabled to avoid a crash. Bug: chromium:1486441 Change-Id: Ie89776d9818d27dc351eff298a44c699e850761b (cherry picked from commit af6dedd)
Configuration menu - View commit details
-
Copy full SHA for 452199c - Browse repository at this point
Copy the full SHA 452199cView commit details -
VP8: disallow thread count changes
Currently allocations are done at encoder creation time. Going from threaded to non-threaded would cause a crash. Bug: chromium:1486441 Change-Id: Ie301c2a70847dff2f0daae408fbef1e4d42e73d4 (cherry picked from commit 3fbd1dc)
Configuration menu - View commit details
-
Copy full SHA for baed121 - Browse repository at this point
Copy the full SHA baed121View commit details
Commits on Sep 29, 2023
-
vp9_alloccommon: clear allocation sizes on free
This fixes reallocations (and avoids potential crashes) if any allocations fails and the application continues to call vpx_codec_decode(). Found with vpx_dec_fuzzer_vp9 & Nallocfuzz (https://github.com/catenacyber/nallocfuzz). Bug: webm:1807 Change-Id: If5dc96b73c02efc94ec84c25eb50d10ad6b645a6 (cherry picked from commit 02ab555)
Configuration menu - View commit details
-
Copy full SHA for a53700e - Browse repository at this point
Copy the full SHA a53700eView commit details -
Fix bug with smaller width bigger size
Fixed previous patch that clusterfuzz failed on. Local fuzzing passing overnight. Bug: webm:1642 Change-Id: If0e08e72abd2e042efe4dcfac21e4cc51afdfdb9 (cherry picked from commit 263682c)
Configuration menu - View commit details
-
Copy full SHA for df9fd9d - Browse repository at this point
Copy the full SHA df9fd9dView commit details -
SO_VERSION_MAJOR = 8 SO_VERSION_MINOR = 0 SO_VERSION_PATCH = 1 The increase of the patch number corresponds to the revision number in the libtool text. 3. If the library source code has changed at all since the last update, then increment revision (‘c:r:a’ becomes ‘c:r+1:a’). Bug: webm:1818 Change-Id: Ia114368e9fd7a908e7fcf6e4d3142f142770e3f4
Configuration menu - View commit details
-
Copy full SHA for 490a706 - Browse repository at this point
Copy the full SHA 490a706View commit details -
Bug: webm:1818 Change-Id: Ic0a943b5d1c69a3621ad3f91012fb5308a0c11f1
Configuration menu - View commit details
-
Copy full SHA for 10b9492 - Browse repository at this point
Copy the full SHA 10b9492View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.13.0...v1.13.1