Use subproject folder name instead of archivesBaseName for maven

This will simplify the modification of the template.

Fixed with #11


nettle: 3.7.3 -> 3.8

Description of changes
Relevant part of the NEWS file: https://git.lysator.liu.se/nettle/nettle/-/blob/master/NEWS#L1-82
Fixes cross-compilation for PowerPC64 big endian ELFv2.
Pinging @vcunat as maintainer.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Question: if this PR gets accepted, should we backport it to 22.05?

I don't think so.  The only bugfix listed is for Windows.

@vcunat: the NEWS file is a bit misleading. The fix I needed is not listed in NEWS, but it is listed in the ChangeLog (L264-267)

Well, it's a question if the overall support of PPC in 22.05 is worth the effort.  I don't know if there's something bigger missing that's important for the whole, e.g. the glibc update or something.

It's true that nettle is a central package, and updating it might unexpectedly break stuff. I don't might keeping my fixes locally and leaving it here until the next NixOS release.

It would be nice if someone tested at least one darwin.  Unfortunately OfBorg is difficult to use for this.  In this case I'd be optimistic and merge anyway, and resolve the unlikely breakage on staging-next.

Built nettle and downstream depender dnsmasq on x86_64-darwin by cherry-picking this back to master to avoid the stdenv rebuild.
Re: backporting, this PR seems like fair game for backporting if it doesn't cause any regressions, but it may be more trouble than it's worth. I usually have a better experience sticking to unstable on exotic systems.


Reduce CMS Docker Image Size

The currently built Docker Image is way too huge for a simple CMS system: bemayr/young-carers-austria-cms:0.1.3, the size is ~600MB.
Possible Solutions

Dockerizing Next.js with Prisma for Production Environments

👎 Runs Prisma Commands at Build Time

Dockerize Next.js With Prisma App

👎 Runs Prisma Commands at Build Time

How did I reduce the docker image size by ~40% for a nextjs app?

👍 uses tj/node-prune to clean node_modules

duniul/clean-modules would be a modern alternative

NextJS Docker image is too big

👎 only applies to Next.js
👍 mentions Next.js' standalone mode (added in Next 12) as it is in with-docker example

Production deployment exceeds 1G in dependencies

👎 Issue is still open
👍 This targets exactly Keystone.js

Roadmap

[x] multi stage docker builds
[ ] clean node_modules
[ ] utilize next.js standalone mode
[ ] get rid of the .next/cache folder concerning webpack
[ ] include only needed prisma providers

Backlinked in #60.


Reserve builds for isolated builds

CLOUDBLD-1732

Signed-off-by: Robert Cerven<EMAIL_ADDRESS>Maintainers will complete the following section

[ ] Commit messages are descriptive enough
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

Cyclomatic complexity of this plugin is overwhelming me. It's very error prone, I'd like to avoid adding more ifs. IMHO this plugin may be good candidate for refactoring.

Agreed, IMO one of the main issues is that half of the run() method is just getting NVR from labels, that should be a separate method for sure. If we don't want to do it in this PR, it would be worth looking at in the future.

rn updated: Reserve builds for isolated builds


Proxy popup not working

VSCode Version: 1.48.0
OS Version: Windows_NT x64 10.0.17134

Steps to Reproduce:

Open Code
The proxy popup appears
try to click ok or cancel and they won't work

Does this issue occur when all extensions are disabled?: No
Version: 1.48.0 (user setup)
Commit: db40434f562994116e5b21c24015a2e40b2504e6
Date: 2020-08-13T07:50:42.600Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.17134

netlog.json.txt

Duplicate of #104603

The #104603 workaround worked for me , now I'm able to click on ok, but the proxy isn't working.
netlog.json.txt


SPARQLProtocolWorker

SPARQLProtocolWorker is a draft for a better, more reliable worker that is tailored towards SPARQL Protocol. Each worker uses a single HttpClient and handles work completion conditions itself. It also covers sending and receiving HTTP request and request bodies that exceed 2GB.
This PR gives an idea what the internals of such a worker could look like. It doesn't provide a full implementation and the code is not yet used within IGUANA.
TODOs:

[ ] Complete TODOs in SPARQLProtocolWorker
[x] Make SPARQLProtocolWorker configurable (and remove all other workers for now)
[ ] Implement LanguageProcessors for xml, csv and tsv SPARQL results
[ ] Port LanguageProcessor for RDF results
[x] Adjust Stresstest to start SPARQLProtocolWorkers
[ ] Adjust Streestest to start a ResponseBodyProcessor per unique (QuerySource,LanguageProcessor)
[ ] write/update tests for all classes touched
[ ] document adjusted behavior
[ ] Ask @MichaelRoeder for a review of BigByteArray{Input,Output}Stream after tests are implemented for them

Future improvements:

allow to select language processors for: RDF and SPARQL-RESULT for each worker. The SPARQLProtocolWorker does content type negotiation based on info from LSQ about the query (basically: if it is a construct query, expect RDF)
Make ResponseBodyProcessor configurable, including timeout for processing after querying is done and number of threads

Should BigByteArrayInputStream and BigByteArrayOutputStream be thread-safe? :thinking:

Hi, I think there not supposed to be thread-safe.

Just as note, some tests don't seem to be running for some reason.


Improve input validation

Fixes #403
Fixes #404
Fixes #405
Fixes #406
Fixes #407

Codecov Report

Merging #408 into master will increase coverage by 0.11%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #408      +/-   ##
==========================================
+ Coverage   99.77%   99.89%   +0.11%
==========================================
  Files          25       25
  Lines        1804     1830      +26
  Branches      287      293       +6
==========================================
+ Hits         1800     1828      +28
+ Misses          2        1       -1
+ Partials        2        1       -1

Flag
Coverage Δ

#unittests
99.89% <100%> (+0.11%)
:arrow_up:

Impacted Files
Coverage Δ

src/schemathesis/cli/callbacks.py
100% <100%> (ø)
:arrow_up:

src/schemathesis/cli/__init__.py
98.33% <100%> (ø)
:arrow_up:

src/schemathesis/_hypothesis.py
100% <100%> (ø)
:arrow_up:

src/schemathesis/utils.py
100% <100%> (ø)
:arrow_up:

src/schemathesis/runner/__init__.py
100% <0%> (+0.83%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6e2e0a2...e3e74c3. Read the comment docs.


Rejected Promises in test causes test to "fail" with error ReferenceError: You are trying to import a file after the Jest environment has been torn down.

New Version
0.72.3
Old Version
0.70.3
Build Target(s)
all
Output of react-native info
System:
  OS: macOS 13.0.1
  CPU: (8) arm64 Apple M1 Pro
  Memory: 77.75 MB / 32.00 GB
  Shell:
    version: 5.8.1
    path: /bin/zsh
Binaries:
  Node:
    version: 16.18.1
    path: ~/.nvm/versions/node/v16.18.1/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.nvm/versions/node/v16.18.1/bin/yarn
  npm:
    version: 8.19.2
    path: ~/.nvm/versions/node/v16.18.1/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.12.1
    path: /Users/mac/.rvm/rubies/ruby-2.7.5/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 22.4
      - iOS 16.4
      - macOS 13.3
      - tvOS 16.4
      - watchOS 9.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2021.3 AI-213.7172.25.2113.9123335
  Xcode:
    version: 14.3.1/14E300c
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.18
    path: /usr/bin/javac
  Ruby:
    version: 2.7.5
    path: /Users/mac/.rvm/rubies/ruby-2.7.5/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.72.3
    wanted: 0.72.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

Issue and Reproduction Steps
Describe the bug
I just upgraded from react native 0.70 to 0.72 and some of my tests that used to pass on my CI started to fail. The test suite passses but the test exits with an error.

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From App.test.js.

      19 |     console.log('ran 2344')
      20 |     } catch (error) {
    > 21 |       Alert.alert('Error', error)
         |       ^
      22 |     }
      23 |
      24 |   }

      at Object.get Alert [as Alert] (node_modules/react-native/index.js:94:12)
      at Alert (App.js:21:7)
          at Generator.throw (<anonymous>)
      at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
      at asyncGeneratorStep (node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)
/Users/mac/Documents/work/side/failedPromises/App.js:26
        _reactNative.Alert.alert('Error', error);
                           ^

TypeError: _reactNative.Alert.alert is not a function
    at /Users/mac/Documents/work/side/failedPromises/App.js:26:28
    at Generator.throw (<anonymous>)
    at asyncGeneratorStep (/Users/mac/Documents/work/side/failedPromises/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
    at _throw (/Users/mac/Documents/work/side/failedPromises/node_modules/@babel/runtime/helpers/asyncToGenerator.js:25:9)

This might be related to this PR https://github.com/facebook/react-native/commit/f1fdc8b9b636e010ae5d5e737fc81a8da8f536d4 cos if I add global.Promise = jest.requireActual('promise'); to my jest.setup.js file the test behave like it was pre 0.71
Expected behavior
Expected bahavior is for this not to break the CI but maybe throw a warning
Steps to Reproduce

clone https://github.com/nero2009/promise-reject-repro
install deps
run npm run test

Versions
npmPackages:
@testing-library/react-native: ^12.2.0 => 12.2.0
react: 18.2.0 => 18.2.0
react-native: 0.72.3 => 0.72.3
react-test-renderer: ^18.2.0 => 18.2.0

@nero2009 Had same issue after upgrading to RN v0.72

FYI @robhogan for the blamed diff removing promise polyfill.

Same issue


Add @method for has_one/belongs_to/has_many/many_many/belongs_many_many

These many-to-something relations can be added with a docbloc like this:
@method ArrayList/ManyManyList|DataObjectName[]

Resolved in commit issue #10


Videos are stuttering starting from 1.8.0

General troubleshooting tips
Before logging an issue please check that:

[x] You have the latest version installed (There may be a beta version that fixes your issue), see here for the latest releases and bug fixes: https://github.com/JohnCoates/Aerial/releases
[x] Your issue isn't already mentioned in our issues. You may find a workaround there or a similar request already made.
[x] Your problem isn't mentioned in the troubleshooting section.

If none of this fixes your issue, tell us about the problem you are experiencing or the feature you'd like to request.
Required information
In order to help us sort your issue, we ask that you provide the following information:

[x] Mac model: MacBook Pro 13-inch 2014
[x] macOS version: macOS Catalina 10.15.3
[x] Monitor setup: Built-in display and external 2560x1440 screen in independent mode

If appropriate, please enable Debug mode and Log to disk in Advanced tab and replicate your bug, then attach the AerialLog.txt file (You can access this file through the Advanced tab).
Description of issue / Feature request
After upgrading from 1.6.1 to 1.8.0 videos are stuttering now making the screensaver completely unusable. It sometimes freezes up to ~1.5 seconds, running for a few seconds with reduced framerate, freezes again. Downgrading to 1.6.1 fixes this issue. It's running completely smooth.

Hi @levrik
That's weird, could you possibly give me a debuglog with 1.8.0 ?
The most likely explanation is that your cache is being ignored and that the stuttering is caused by the videos streaming. I would double check that your videos are not streaming with 1.8.0. Especially if you store your videos outside of the sandboxed container.

@glouel I have streaming disabled in the settings.

Ok, please send me a debuglog if you can with 1.8.0 (enable that in Advanced tab). Aerial may still stream if there are no videos at all cached, so it's not 100% out of the question.
Noted for the clock, in general the video playback is completely handled by Apple's API so it's very likely still that you are steaming. Thanks !

2020-03-02 14:37:08.026 : avInit .saver (0.0, 0.0, 2560.0, 1440.0) p: true o: false
2020-03-02 14:37:08.027 : <AerialView: 0x7f9877f0e980> AerialView setup init (V1.8.0) preview: false
2020-03-02 14:37:08.027 : Probing availability of an update
2020-03-02 14:37:08.028 : Checking for update (probe mode)
2020-03-02 14:37:08.030 : Time Management initialized
2020-03-02 14:37:08.030 : Display Detection initialized
2020-03-02 14:37:08.031 : ***Display Detection***
2020-03-02 14:37:08.031 : 2 display(s) detected
2020-03-02 14:37:08.031 : 1cm = 48.425197577667205 points
2020-03-02 14:37:08.032 : npass: dict [__C.NSDeviceDescriptionKey(_rawValue: NSDeviceBitsPerSample): 8, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceColorSpaceName): NSCalibratedRGBColorSpace, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceResolution): NSSize: {72, 72}, __C.NSDeviceDescriptionKey(_rawValue: NSScreenNumber): 724042126, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceIsScreen): YES, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceSize): NSSize: {2560, 1440}]
2020-03-02 14:37:08.032 :        bottomLeftFrame (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 14:37:08.032 : npass: dict [__C.NSDeviceDescriptionKey(_rawValue: NSDeviceBitsPerSample): 8, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceColorSpaceName): NSCalibratedRGBColorSpace, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceResolution): NSSize: {144, 144}, __C.NSDeviceDescriptionKey(_rawValue: NSScreenNumber): 69731840, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceIsScreen): YES, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceSize): NSSize: {1440, 900}]
2020-03-02 14:37:08.033 :        bottomLeftFrame (687.0, -900.0, 1440.0, 900.0)
2020-03-02 14:37:08.033 : src orig : (0.0, 0.0)
2020-03-02 14:37:08.034 : left 0.0 below 1.0
2020-03-02 14:37:08.034 : src orig : (687.0, -900.0)
2020-03-02 14:37:08.035 : left 0.0 below 0.0
2020-03-02 14:37:08.035 : [id=724042126, width=2560, height=1440, bottomLeftFrame=(0.0, 0.0, 2560.0, 1440.0), topRightCorner=(2560.0, 1440.0), isMain=true, backingScaleFactor=1.0]
2020-03-02 14:37:08.036 : [id=69731840, width=1440, height=900, bottomLeftFrame=(687.0, -900.0, 1440.0, 900.0), topRightCorner=(2127.0, 0.0), isMain=false, backingScaleFactor=2.0]
2020-03-02 14:37:08.036 : (0.0, -900.0, 2560.0, 2485.2755927330018)
2020-03-02 14:37:08.037 : ***Display Detection Done***
2020-03-02 14:37:08.037 : Using : Optional([id=724042126, width=2560, height=1440, bottomLeftFrame=(0.0, 0.0, 2560.0, 1440.0), topRightCorner=(2560.0, 1440.0), isMain=true, backingScaleFactor=1.0])
2020-03-02 14:37:08.037 : <AerialView: 0x7f9877f0e980> setting up player layer with bounds/frame: (0.0, 0.0, 2560.0, 1440.0) / (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 14:37:08.039 : allDisplays
2020-03-02 14:37:08.040 : allDisplays
2020-03-02 14:37:08.040 : allDisplays
2020-03-02 14:37:08.041 : Using dot workaround for video driver corruption
2020-03-02 14:37:08.041 : Manifest init
2020-03-02 14:37:08.042 : app support exists
2020-03-02 14:37:08.042 : No customvideos.json at : /Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application Support/Aerial/customvideos.json
2020-03-02 14:37:08.043 : isManifestCached 10 true
2020-03-02 14:37:08.043 : isManifestCached 11 true
2020-03-02 14:37:08.044 : isManifestCached 12 true
2020-03-02 14:37:08.045 : isManifestCached 13 true
2020-03-02 14:37:08.045 : 2020-03-02
2020-03-02 14:37:08.046 : Interval : Optional(-52627.27096295357)
2020-03-02 14:37:08.046 : No need to check for new videos
2020-03-02 14:37:08.047 : Manifests files were not loaded in class
2020-03-02 14:37:08.047 : Files were not already loaded in memory
2020-03-02 14:37:08.048 : Manifests are cached on disk, loading
2020-03-02 14:37:08.048 : Poi Strings Provider initialized
2020-03-02 14:37:08.049 : Language overriden to Optional("en")
2020-03-02 14:37:08.049 : Community Language overriden to : en
2020-03-02 14:37:08.050 : path : /Users/levrik/Library/Screen Savers/Aerial.saver/Contents/Resources/en.json
2020-03-02 14:37:08.050 : Community JSON : 99 entries
2020-03-02 14:37:08.050 : Using exiting customCacheDirectory : /Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application Support/Aerial
2020-03-02 14:37:08.051 : cache to be used : Optional("/Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application Support/Aerial")
2020-03-02 14:37:08.051 : Total videos processed : 99 callbacks : 0
2020-03-02 14:37:08.052 : <AerialView: 0x7f9877f0e980> Setting player for all player layers in []
2020-03-02 14:37:08.052 : initvideocache
2020-03-02 14:37:08.053 : cached video file with length: 169454212
2020-03-02 14:37:08.054 : <AerialView: 0x7f9877f0e980> playing video (OFFLINE MODE) : file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/BO_A018_C029_SDR_20190812_SDR_2K_AVC.mov
2020-03-02 14:37:08.055 : <AerialView: 0x7f9877f0e980> observing current item <AVPlayerItem: 0x600000d21480, asset = <AVURLAsset: 0x600000f6e3e0, URL = file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/BO_A018_C029_SDR_20190812_SDR_2K_AVC.mov>>
2020-03-02 14:37:08.055 : <AerialView: 0x7f9877f0e980> observeValue Optional("readyForDisplay") false (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 14:37:08.056 : AssetLoaderDelegate deinit
2020-03-02 14:37:08.057 : <AerialView: 0x7f9877f0e980> backing change 1.0 isDisabled: false frame: (0.0, 0.0, 2560.0, 1440.0) preview: false
2020-03-02 14:37:08.602 : avInit .saver (687.0, -900.0, 1440.0, 900.0) p: true o: false
2020-03-02 14:37:08.603 : <AerialView: 0x7f9877d152d0> AerialView setup init (V1.8.0) preview: false
2020-03-02 14:37:08.603 : Probing availability of an update
2020-03-02 14:37:08.603 : Checking for update (probe mode)
2020-03-02 14:37:08.604 : Using : Optional([id=69731840, width=1440, height=900, bottomLeftFrame=(687.0, -900.0, 1440.0, 900.0), topRightCorner=(2127.0, 0.0), isMain=false, backingScaleFactor=2.0])
2020-03-02 14:37:08.604 : <AerialView: 0x7f9877d152d0> setting up player layer with bounds/frame: (0.0, 0.0, 1440.0, 900.0) / (0.0, 0.0, 1440.0, 900.0)
2020-03-02 14:37:08.605 : allDisplays
2020-03-02 14:37:08.605 : allDisplays
2020-03-02 14:37:08.605 : allDisplays
2020-03-02 14:37:08.606 : Using dot workaround for video driver corruption
2020-03-02 14:37:08.606 : <AerialView: 0x7f9877d152d0> Setting player for all player layers in []
2020-03-02 14:37:08.607 : initvideocache
2020-03-02 14:37:08.608 : cached video file with length: 368658451
2020-03-02 14:37:08.608 : <AerialView: 0x7f9877d152d0> playing video (OFFLINE MODE) : file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/FK_U009_C004_SDR_20191220_SDR_2K_AVC.mov
2020-03-02 14:37:08.609 : <AerialView: 0x7f9877d152d0> observing current item <AVPlayerItem: 0x600000d21600, asset = <AVURLAsset: 0x600000f6f880, URL = file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/FK_U009_C004_SDR_20191220_SDR_2K_AVC.mov>>
2020-03-02 14:37:08.609 : <AerialView: 0x7f9877d152d0> observeValue Optional("readyForDisplay") false (687.0, -900.0, 1440.0, 900.0)
2020-03-02 14:37:08.609 : AssetLoaderDelegate deinit
2020-03-02 14:37:08.610 : <AerialView: 0x7f9877d152d0> backing change 2.0 isDisabled: false frame: (0.0, 0.0, 1440.0, 900.0) preview: false
2020-03-02 14:37:08.626 : <AerialView: 0x7f9877f0e980> startAnimation frame (0.0, 0.0, 2560.0, 1440.0) bounds (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 14:37:08.652 : <AerialView: 0x7f9877f0e980> observeValue Optional("readyForDisplay") true (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 14:37:08.652 : start playback: (0.0, 0.0, 2560.0, 1440.0) (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 14:37:08.654 : //////// No update is available !
2020-03-02 14:37:08.666 : <AerialView: 0x7f9877d152d0> observeValue Optional("readyForDisplay") true (0.0, 0.0, 1440.0, 900.0)

Ok, doesn't look like you are streaming in that instance.
It looks like you are using 1080p H.264 as your video setting, is that correct ? Can you double check the settings ? Around 1.7.0 I did reset the video setting preference (not backward compatible with 1.6), so one scenario I can think of is you had for example 1080pHEVC previously, updated, it was reset to 1080pH264 and started restreaming (and recaching) your videos again (that, or the other way around). Could you look into that ?
Both screens freezing is normal as it's using only one player for both views in the background to optimize for power consumption ;)

I already deleted the whole cache and re-downloaded with 1080p H.264 set.
Didn't help.

I see ! Sorry about all that and sorry to insist, but could you give me a log where the slowdown is occuring ? It didn't seem to register in the log you sent me (there should be some lines mentionning the framerate going to 0).
Again, sorry about that, assuming your videos are cached and you are using H.264, there's no issue I know of right now, so it could be something new where a log would help.
There are a few things that could slow down Aerial in the background (iPhotos processing your videos/photos), but the issue would equally happen with any Aerial versions. If you can consistently reproduce the issue only with 1.8.0 then that's not it (but if it happened only a few times, could be that). Always worth mentioning.

I cleared the log file, triggered the screen saver and sent you the then newly created log file.
I don't use iPhotos. The default Photos app is not even set up.

Understood, sorry if I wasn't clear.
What I meant was, that log doesn't show any freeze, it just shows about 1 second of startup time. A log where you saw the slowdown happening (optionnally, look at the time it happens and report it too) is what I was hoping for ? This may take some time to gather so no hurry.
Sorry again about your issue, hopefully we can track it down.

The stuttering actually happens every time I start the screensaver. So of course the log file I've sent you was captured while the issue was happening.
I just verified. 1.6.1 is behaving completely smoothly. I'll try to upgrade to intermediate versions to track down when it starts to happen.

Okay. I can confirm. Last version running smoothly is 1.7.1. The stuttering starts with version 1.8.0.

Running smooth

Videos are stuttering

Maybe the log is truncated, what you pasted goes from 14:37:08.026 to 14:37:08.666, so about half a second. Sometimes the writes are delayed for a bit, you didn't even get the "start playback" log entry, was what I was getting to (so no chance to get a stall message).
In any case, looks like you found what's causing it. What this does is launch a network check for a new version with Sparkle. It's possible that on your laptop it's taxing the CPU a bit, although it's a bit weird to me...
Do you happen to run a firewall (something like Little Snitch) on your Mac by any chance ?

Nope. No custom firewall installed.
But the version check. How often is it happening? The stuttering seems to go on forever. At least I let it run for like 5 minutes and it didn't get really better. Just the full freezes seem to stop after ~30 seconds.
Then it continues with reduced framerate. With the update notifier disabled it runs smoothly. No freezes, no reduced framerate.
Should I try to get another log for you?

Ok that's a bit crazy then. Another log may help yes, although it's interesting to note that in your log, the check was done even before the playback started (it's really just checking a file on github if there's no version).
You have this entry :
2020-03-02 14:37:08.654 : //////// No update is available !

Which shows that check was done, and playback wasn't even started (which happens most of the time with a good connexion and github working well)... The other entries in your logjust show the preloading stuff. So that's super weird...
Currently the check happens at every startup if enabled (and I enabled it by default).
Please try and record another log if you have some time, and I'll have another look. There's definitely something weird going on here, could be related to something going awry with that check on multi monitor setups maybe... Very weird. Sorry about the issue, that's definitely a bit wild I'll try to think about it.
Thanks for your report and very quick checks.

2020-03-02 15:52:10.586 : UI allowScreenSaverModeUpdatesChange: true
2020-03-02 15:52:14.219 : <AerialView: 0x7f94a6f074e0> startAnimation frame (0.0, 0.0, 296.0, 184.0) bounds (0.0, 0.0, 296.0, 184.0)
2020-03-02 15:52:14.220 : restarting playback
2020-03-02 15:52:15.034 : <AerialView: 0x7f94a6f074e0> stopAnimation
2020-03-02 15:52:47.703 : avInit .saver (0.0, 0.0, 2560.0, 1440.0) p: true o: false
2020-03-02 15:52:47.703 : <AerialView: 0x7ff521707ca0> AerialView setup init (V1.8.0) preview: false
2020-03-02 15:52:47.704 : Probing availability of an update
2020-03-02 15:52:47.704 : Checking for update (probe mode)
2020-03-02 15:52:47.707 : Time Management initialized
2020-03-02 15:52:47.707 : Display Detection initialized
2020-03-02 15:52:47.708 : ***Display Detection***
2020-03-02 15:52:47.708 : 2 display(s) detected
2020-03-02 15:52:47.709 : 1cm = 48.425197577667205 points
2020-03-02 15:52:47.709 : npass: dict [__C.NSDeviceDescriptionKey(_rawValue: NSDeviceIsScreen): YES, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceBitsPerSample): 8, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceResolution): NSSize: {72, 72}, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceSize): NSSize: {2560, 1440}, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceColorSpaceName): NSCalibratedRGBColorSpace, __C.NSDeviceDescriptionKey(_rawValue: NSScreenNumber): 724042126]
2020-03-02 15:52:47.709 :        bottomLeftFrame (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:52:47.710 : npass: dict [__C.NSDeviceDescriptionKey(_rawValue: NSDeviceIsScreen): YES, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceBitsPerSample): 8, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceResolution): NSSize: {144, 144}, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceSize): NSSize: {1440, 900}, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceColorSpaceName): NSCalibratedRGBColorSpace, __C.NSDeviceDescriptionKey(_rawValue: NSScreenNumber): 69731840]
2020-03-02 15:52:47.710 :        bottomLeftFrame (687.0, -900.0, 1440.0, 900.0)
2020-03-02 15:52:47.710 : src orig : (0.0, 0.0)
2020-03-02 15:52:47.711 : left 0.0 below 1.0
2020-03-02 15:52:47.711 : src orig : (687.0, -900.0)
2020-03-02 15:52:47.711 : left 0.0 below 0.0
2020-03-02 15:52:47.712 : [id=724042126, width=2560, height=1440, bottomLeftFrame=(0.0, 0.0, 2560.0, 1440.0), topRightCorner=(2560.0, 1440.0), isMain=true, backingScaleFactor=1.0]
2020-03-02 15:52:47.712 : [id=69731840, width=1440, height=900, bottomLeftFrame=(687.0, -900.0, 1440.0, 900.0), topRightCorner=(2127.0, 0.0), isMain=false, backingScaleFactor=2.0]
2020-03-02 15:52:47.713 : (0.0, -900.0, 2560.0, 2485.2755927330018)
2020-03-02 15:52:47.713 : ***Display Detection Done***
2020-03-02 15:52:47.714 : Using : Optional([id=724042126, width=2560, height=1440, bottomLeftFrame=(0.0, 0.0, 2560.0, 1440.0), topRightCorner=(2560.0, 1440.0), isMain=true, backingScaleFactor=1.0])
2020-03-02 15:52:47.714 : <AerialView: 0x7ff521707ca0> setting up player layer with bounds/frame: (0.0, 0.0, 2560.0, 1440.0) / (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:52:47.716 : allDisplays
2020-03-02 15:52:47.717 : allDisplays
2020-03-02 15:52:47.717 : allDisplays
2020-03-02 15:52:47.717 : Using dot workaround for video driver corruption
2020-03-02 15:52:47.718 : Manifest init
2020-03-02 15:52:47.718 : app support exists
2020-03-02 15:52:47.719 : No customvideos.json at : /Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application Support/Aerial/customvideos.json
2020-03-02 15:52:47.720 : isManifestCached 10 true
2020-03-02 15:52:47.720 : isManifestCached 11 true
2020-03-02 15:52:47.721 : isManifestCached 12 true
2020-03-02 15:52:47.721 : isManifestCached 13 true
2020-03-02 15:52:47.723 : 2020-03-02
2020-03-02 15:52:47.723 : Interval : Optional(-57166.80578303337)
2020-03-02 15:52:47.724 : No need to check for new videos
2020-03-02 15:52:47.724 : Manifests files were not loaded in class
2020-03-02 15:52:47.725 : Files were not already loaded in memory
2020-03-02 15:52:47.725 : Manifests are cached on disk, loading
2020-03-02 15:52:47.726 : Poi Strings Provider initialized
2020-03-02 15:52:47.726 : Language overriden to Optional("en")
2020-03-02 15:52:47.727 : Community Language overriden to : en
2020-03-02 15:52:47.727 : path : /Users/levrik/Library/Screen Savers/Aerial.saver/Contents/Resources/en.json
2020-03-02 15:52:47.728 : Community JSON : 99 entries
2020-03-02 15:52:47.728 : Using exiting customCacheDirectory : /Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application Support/Aerial
2020-03-02 15:52:47.728 : cache to be used : Optional("/Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application Support/Aerial")
2020-03-02 15:52:47.729 : Total videos processed : 99 callbacks : 0
2020-03-02 15:52:47.729 : <AerialView: 0x7ff521707ca0> Setting player for all player layers in []
2020-03-02 15:52:47.729 : initvideocache
2020-03-02 15:52:47.730 : cached video file with length: 252890736
2020-03-02 15:52:47.730 : <AerialView: 0x7ff521707ca0> playing video (OFFLINE MODE) : file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/comp_A103_C002_0205DG_v12_SDR_FINAL_20180706_SDR_2K_AVC.mov
2020-03-02 15:52:47.730 : <AerialView: 0x7ff521707ca0> observing current item <AVPlayerItem: 0x600002d5d200, asset = <AVURLAsset: 0x600002f6dac0, URL = file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/comp_A103_C002_0205DG_v12_SDR_FINAL_20180706_SDR_2K_AVC.mov>>
2020-03-02 15:52:47.731 : <AerialView: 0x7ff521707ca0> observeValue Optional("readyForDisplay") false (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:52:47.731 : AssetLoaderDelegate deinit
2020-03-02 15:52:47.732 : <AerialView: 0x7ff521707ca0> backing change 1.0 isDisabled: false frame: (0.0, 0.0, 2560.0, 1440.0) preview: false
2020-03-02 15:52:48.882 : avInit .saver (687.0, -900.0, 1440.0, 900.0) p: true o: false
2020-03-02 15:52:48.883 : <AerialView: 0x7ff521419930> AerialView setup init (V1.8.0) preview: false
2020-03-02 15:52:48.883 : Probing availability of an update
2020-03-02 15:52:48.884 : Checking for update (probe mode)
2020-03-02 15:52:48.884 : Using : Optional([id=69731840, width=1440, height=900, bottomLeftFrame=(687.0, -900.0, 1440.0, 900.0), topRightCorner=(2127.0, 0.0), isMain=false, backingScaleFactor=2.0])
2020-03-02 15:52:48.884 : <AerialView: 0x7ff521419930> setting up player layer with bounds/frame: (0.0, 0.0, 1440.0, 900.0) / (0.0, 0.0, 1440.0, 900.0)
2020-03-02 15:52:48.885 : allDisplays
2020-03-02 15:52:48.886 : allDisplays
2020-03-02 15:52:48.886 : allDisplays
2020-03-02 15:52:48.887 : Using dot workaround for video driver corruption
2020-03-02 15:52:48.888 : <AerialView: 0x7ff521419930> Setting player for all player layers in []
2020-03-02 15:52:48.889 : initvideocache
2020-03-02 15:52:48.891 : cached video file with length: 400154051
2020-03-02 15:52:48.892 : <AerialView: 0x7ff521419930> playing video (OFFLINE MODE) : file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/comp_LA_A011_C003_DGRN_LNFIX_STAB_v57_SDR_PS_20181002_SDR_2K_AVC.mov
2020-03-02 15:52:48.894 : <AerialView: 0x7ff521419930> observing current item <AVPlayerItem: 0x600002d519d0, asset = <AVURLAsset: 0x600002f736c0, URL = file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/comp_LA_A011_C003_DGRN_LNFIX_STAB_v57_SDR_PS_20181002_SDR_2K_AVC.mov>>
2020-03-02 15:52:48.896 : <AerialView: 0x7ff521419930> observeValue Optional("readyForDisplay") false (687.0, -900.0, 1440.0, 900.0)
2020-03-02 15:52:48.898 : AssetLoaderDelegate deinit
2020-03-02 15:52:48.902 : <AerialView: 0x7ff521419930> backing change 2.0 isDisabled: false frame: (0.0, 0.0, 1440.0, 900.0) preview: false
2020-03-02 15:52:48.931 : <AerialView: 0x7ff521707ca0> startAnimation frame (0.0, 0.0, 2560.0, 1440.0) bounds (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:52:48.940 : <AerialView: 0x7ff521707ca0> observeValue Optional("readyForDisplay") true (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:52:48.941 : start playback: (0.0, 0.0, 2560.0, 1440.0) (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:52:48.942 : //////// No update is available !
2020-03-02 15:52:48.956 : <AerialView: 0x7ff521419930> observeValue Optional("readyForDisplay") true (0.0, 0.0, 1440.0, 900.0)
2020-03-02 15:52:48.957 : start playback: (0.0, 0.0, 1440.0, 900.0) (0.0, 0.0, 1440.0, 900.0)
2020-03-02 15:52:49.261 : <AerialView: 0x7ff521419930> startAnimation frame (0.0, 0.0, 1440.0, 900.0) bounds (0.0, 0.0, 1440.0, 900.0)
2020-03-02 15:53:25.314 : <AerialView: 0x7f94a6f074e0> startAnimation frame (0.0, 0.0, 296.0, 184.0) bounds (0.0, 0.0, 296.0, 184.0)
2020-03-02 15:53:25.316 : restarting playback
2020-03-02 15:54:31.651 : <AerialView: 0x7f94a6f074e0> stopAnimation
2020-03-02 15:54:34.571 : UI allowScreenSaverModeUpdatesChange: false
2020-03-02 15:54:38.095 : <AerialView: 0x7f94a6f074e0> startAnimation frame (0.0, 0.0, 296.0, 184.0) bounds (0.0, 0.0, 296.0, 184.0)
2020-03-02 15:54:38.096 : restarting playback
2020-03-02 15:54:38.825 : <AerialView: 0x7f94a6f074e0> stopAnimation
2020-03-02 15:54:47.110 : avInit .saver (0.0, 0.0, 2560.0, 1440.0) p: true o: false
2020-03-02 15:54:47.111 : <AerialView: 0x7fea2f40c0d0> AerialView setup init (V1.8.0) preview: false
2020-03-02 15:54:47.111 : Time Management initialized
2020-03-02 15:54:47.111 : Display Detection initialized
2020-03-02 15:54:47.112 : ***Display Detection***
2020-03-02 15:54:47.112 : 2 display(s) detected
2020-03-02 15:54:47.113 : 1cm = 48.425197577667205 points
2020-03-02 15:54:47.113 : npass: dict [__C.NSDeviceDescriptionKey(_rawValue: NSScreenNumber): 724042126, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceBitsPerSample): 8, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceIsScreen): YES, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceResolution): NSSize: {72, 72}, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceColorSpaceName): NSCalibratedRGBColorSpace, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceSize): NSSize: {2560, 1440}]
2020-03-02 15:54:47.113 :        bottomLeftFrame (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:54:47.114 : npass: dict [__C.NSDeviceDescriptionKey(_rawValue: NSScreenNumber): 69731840, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceBitsPerSample): 8, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceIsScreen): YES, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceResolution): NSSize: {144, 144}, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceColorSpaceName): NSCalibratedRGBColorSpace, __C.NSDeviceDescriptionKey(_rawValue: NSDeviceSize): NSSize: {1440, 900}]
2020-03-02 15:54:47.114 :        bottomLeftFrame (687.0, -900.0, 1440.0, 900.0)
2020-03-02 15:54:47.115 : src orig : (0.0, 0.0)
2020-03-02 15:54:47.116 : left 0.0 below 1.0
2020-03-02 15:54:47.117 : src orig : (687.0, -900.0)
2020-03-02 15:54:47.118 : left 0.0 below 0.0
2020-03-02 15:54:47.118 : [id=724042126, width=2560, height=1440, bottomLeftFrame=(0.0, 0.0, 2560.0, 1440.0), topRightCorner=(2560.0, 1440.0), isMain=true, backingScaleFactor=1.0]
2020-03-02 15:54:47.119 : [id=69731840, width=1440, height=900, bottomLeftFrame=(687.0, -900.0, 1440.0, 900.0), topRightCorner=(2127.0, 0.0), isMain=false, backingScaleFactor=2.0]
2020-03-02 15:54:47.119 : (0.0, -900.0, 2560.0, 2485.2755927330018)
2020-03-02 15:54:47.120 : ***Display Detection Done***
2020-03-02 15:54:47.121 : Using : Optional([id=724042126, width=2560, height=1440, bottomLeftFrame=(0.0, 0.0, 2560.0, 1440.0), topRightCorner=(2560.0, 1440.0), isMain=true, backingScaleFactor=1.0])
2020-03-02 15:54:47.122 : <AerialView: 0x7fea2f40c0d0> setting up player layer with bounds/frame: (0.0, 0.0, 2560.0, 1440.0) / (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:54:47.124 : allDisplays
2020-03-02 15:54:47.125 : allDisplays
2020-03-02 15:54:47.125 : Using dot workaround for video driver corruption
2020-03-02 15:54:47.127 : Manifest init
2020-03-02 15:54:47.129 : app support exists
2020-03-02 15:54:47.130 : No customvideos.json at : /Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application Support/Aerial/customvideos.json
2020-03-02 15:54:47.131 : isManifestCached 10 true
2020-03-02 15:54:47.132 : isManifestCached 11 true
2020-03-02 15:54:47.133 : isManifestCached 12 true
2020-03-02 15:54:47.134 : isManifestCached 13 true
2020-03-02 15:54:47.134 : 2020-03-02
2020-03-02 15:54:47.135 : Interval : Optional(-57285.395172953606)
2020-03-02 15:54:47.136 : No need to check for new videos
2020-03-02 15:54:47.136 : Manifests files were not loaded in class
2020-03-02 15:54:47.137 : Files were not already loaded in memory
2020-03-02 15:54:47.139 : Manifests are cached on disk, loading
2020-03-02 15:54:47.140 : Poi Strings Provider initialized
2020-03-02 15:54:47.142 : Language overriden to Optional("en")
2020-03-02 15:54:47.144 : Community Language overriden to : en
2020-03-02 15:54:47.146 : path : /Users/levrik/Library/Screen Savers/Aerial.saver/Contents/Resources/en.json
2020-03-02 15:54:47.146 : Community JSON : 99 entries
2020-03-02 15:54:47.147 : Using exiting customCacheDirectory : /Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application Support/Aerial
2020-03-02 15:54:47.147 : cache to be used : Optional("/Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application Support/Aerial")
2020-03-02 15:54:47.148 : Total videos processed : 99 callbacks : 0
2020-03-02 15:54:47.148 : <AerialView: 0x7fea2f40c0d0> Setting player for all player layers in []
2020-03-02 15:54:47.149 : initvideocache
2020-03-02 15:54:47.149 : cached video file with length: 619839252
2020-03-02 15:54:47.150 : <AerialView: 0x7fea2f40c0d0> playing video (OFFLINE MODE) : file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/comp_HK_H004_C001_PSNK_DENOISE_v14_SDR_PS_FINAL_20180731_SDR_2K_AVC.mov
2020-03-02 15:54:47.150 : <AerialView: 0x7fea2f40c0d0> observing current item <AVPlayerItem: 0x600000b3cdd0, asset = <AVURLAsset: 0x60000091eac0, URL = file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/comp_HK_H004_C001_PSNK_DENOISE_v14_SDR_PS_FINAL_20180731_SDR_2K_AVC.mov>>
2020-03-02 15:54:47.151 : <AerialView: 0x7fea2f40c0d0> observeValue Optional("readyForDisplay") false (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:54:47.151 : AssetLoaderDelegate deinit
2020-03-02 15:54:47.152 : <AerialView: 0x7fea2f40c0d0> backing change 1.0 isDisabled: false frame: (0.0, 0.0, 2560.0, 1440.0) preview: false
2020-03-02 15:54:47.857 : avInit .saver (687.0, -900.0, 1440.0, 900.0) p: true o: false
2020-03-02 15:54:47.857 : <AerialView: 0x7fea2f513dd0> AerialView setup init (V1.8.0) preview: false
2020-03-02 15:54:47.858 : Using : Optional([id=69731840, width=1440, height=900, bottomLeftFrame=(687.0, -900.0, 1440.0, 900.0), topRightCorner=(2127.0, 0.0), isMain=false, backingScaleFactor=2.0])
2020-03-02 15:54:47.858 : <AerialView: 0x7fea2f513dd0> setting up player layer with bounds/frame: (0.0, 0.0, 1440.0, 900.0) / (0.0, 0.0, 1440.0, 900.0)
2020-03-02 15:54:47.859 : allDisplays
2020-03-02 15:54:47.859 : allDisplays
2020-03-02 15:54:47.859 : Using dot workaround for video driver corruption
2020-03-02 15:54:47.860 : <AerialView: 0x7fea2f513dd0> Setting player for all player layers in []
2020-03-02 15:54:47.860 : initvideocache
2020-03-02 15:54:47.861 : cached video file with length: 413610907
2020-03-02 15:54:47.862 : <AerialView: 0x7fea2f513dd0> playing video (OFFLINE MODE) : file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/comp_DB_D008_C010_PSNK_v21_SDR_PS_20180914_F0F16157_SDR_2K_AVC.mov
2020-03-02 15:54:47.862 : <AerialView: 0x7fea2f513dd0> observing current item <AVPlayerItem: 0x600000b29690, asset = <AVURLAsset: 0x600000919a00, URL = file:///Users/levrik/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Application%20Support/Aerial/comp_DB_D008_C010_PSNK_v21_SDR_PS_20180914_F0F16157_SDR_2K_AVC.mov>>
2020-03-02 15:54:47.862 : <AerialView: 0x7fea2f513dd0> observeValue Optional("readyForDisplay") false (687.0, -900.0, 1440.0, 900.0)
2020-03-02 15:54:47.863 : AssetLoaderDelegate deinit
2020-03-02 15:54:47.865 : <AerialView: 0x7fea2f513dd0> backing change 2.0 isDisabled: false frame: (0.0, 0.0, 1440.0, 900.0) preview: false
2020-03-02 15:54:47.878 : <AerialView: 0x7fea2f40c0d0> startAnimation frame (0.0, 0.0, 2560.0, 1440.0) bounds (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:54:47.895 : <AerialView: 0x7fea2f40c0d0> observeValue Optional("readyForDisplay") true (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:54:47.896 : start playback: (0.0, 0.0, 2560.0, 1440.0) (0.0, 0.0, 2560.0, 1440.0)
2020-03-02 15:54:47.910 : <AerialView: 0x7fea2f513dd0> observeValue Optional("readyForDisplay") true (0.0, 0.0, 1440.0, 900.0)
2020-03-02 15:54:47.911 : start playback: (0.0, 0.0, 1440.0, 900.0) (0.0, 0.0, 1440.0, 900.0)
2020-03-02 15:54:48.363 : <AerialView: 0x7fea2f513dd0> startAnimation frame (0.0, 0.0, 1440.0, 900.0) bounds (0.0, 0.0, 1440.0, 900.0)
2020-03-02 15:55:00.152 : <AerialView: 0x7f94a6f074e0> startAnimation frame (0.0, 0.0, 296.0, 184.0) bounds (0.0, 0.0, 296.0, 184.0)
2020-03-02 15:55:00.153 : restarting playback

I've included the logs of two runs. One with the update check enabled, one disabled.
You should be able to see from the logs when I changed it.

Thanks for the log, I did see the two runs with and without the check. But I don't see anything wrong in the first run, sadly.
I suggest you keep the option disabled for now.
I'll try and reproduce with an external monitor here this week, to see if this is related, and will let you know what I find.

Hi, just want to share that I experienced the same issue with ver 1.8.2 on my 13' RMBP, early 2015. Unticking the notifying new versions does fix the problem.

Thanks for the heads up @yueqianh  ! Do you use an external monitor ?

Hello good sir,
I am getting frame rate stuttering on an iMac Pro (late 2017, 32GB RAM with the VEGA 56). I was running Aerial 1.8.2 -- I tried upgrading to 1.8.3 beta 4 as well, with no change. Screen saver format prefs are: 4K HEVC non-HDR
Running Catalina 10.15.4
Trying to not "stream" anything (I have the settings to pre-cache videos, to the best of my knowledge).
Everything works fine for several "initiations" of Aerial after a macOS reboot, however after several instances of loading smoothly, they will start to stutter every time the screen saver comes up, until rebooting the machine.
Any suggestions welcome! Thank you

Hi @teleport9000
First, can you check if Aerial's Updates tab, if you have "When the screensaver runs" checked near the bottom of the screen ? If so please disable it and try again and let me know if you still experience the issue ?

@glouel Thanks for the quick response. Attached are the settings I have currently.
I actually just rebooted. Playback was smooth for one time (initiating screen saver via hot corner). On subsequent runs, it's now stuttering again (on the second Aerial run, after reboot). (1.8.3 beta 4)
BTW, when working smoothly, the GPU usage percentage seems to hover around 33% for 1 monitor doing 4K HEVC playback, the Skylake Xeon's in the iMac Pro's don't support hardware 10bit HEVC decoding. I think Apple has the GPU going it, so running two independent screens has the GPU plugging along at around 60-70%, regardless of wether the resulting videos are stuttering, or smooth.

I actually just rebooted. Playback was smooth for one time (initiating screen saver via hot corner). On subsequent runs, it's now stuttering again (on the second Aerial run, after reboot). (1.8.3 beta 4)

I see, it kinda sounds like the delayed tasks that macOS runs.

BTW, when working smoothly, the GPU usage percentage seems to hover around 33% for 1 monitor doing 4K HEVC playback, the Skylake Xeon's in the iMac Pro's don't support hardware 10bit HEVC decoding. I think Apple has the GPU going it, so running two independent screens has the GPU plugging along at around 60-70%, regardless of wether the resulting videos are stuttering, or smooth.

So just to give you a bit more feedback on this, on an iMac Pro, you don't have a GPU on your Intel CPU as far as I remember (99.99% sure), so it's always deferring to the GPU. But the GPU usage you can't trust, as GPU video decoding is done by a fixed unit and not by the "GPU" units if that makes any sense.

Edit in response to your edit: I do have my "system photo library" (that Photos.app pulls from) on an external SSD. If that could possible matter.

It might, my question would be, do you often add videos and photos to your library ? Because the analysis of those videos is usually what throws off Aerial. There was another user that had the issue here  if you are interested in reading more details : https://github.com/JohnCoates/Aerial/issues/882
Long story short, if you see that mediaanalysisd is running while the screensaver is running, then that might be your issue. There's more on how to disable those recogntion things (those are the background process that fill in the people/object search in photos/videos, which is done on all your Apple devices for your whole library, including your mac)

You were correct, I was able to resolve the issue (so far), by just ejecting the external volume that my macOS Photos library resides on (thereby stopping media/photoanalysisd).
I never did see the CPU spiking, to try to compensate (if media/photoanalysisd was indeed precluding Aerial from accessing GPU acceleration).
Correct, no built in Intel graphics on the iMac Pro.
Ok thanks, I did not know that the AMD chips had dedicated playback/transcode units (I guess similar to NVENC on nvidia?)
I've attached an annotated screenshot of where I was getting those GPU usage figures from. iStat Menus. The clock speed reported for the main GPU remains low throughout Aerial playback (like 15-100MHz), even though the "usage percentage" increases the more screens that I add.

You were correct, I was able to resolve the issue (so far), by just ejecting the external volume that my macOS Photos library resides on (thereby stopping media/photoanalysisd).

Awesome ! You can disable it as per the thread I linked so it doesn't run when the screensaver runs.

I never did see the CPU spiking, to try to compensate (if media/photoanalysisd was indeed precluding Aerial from accessing GPU acceleration).

It should be mild if anything on such a CPU. I do have a late 2015 iMac with a basic Skylake Core i5  here, and it seemlessly decodes 4K HEVC/HDR on the CPU as it's integrated GPU doesn't do HEVC.

Ok thanks, I did not know that the AMD chips had dedicated playback/transcode units (I guess similar to NVENC on nvidia?)

Yep exactly the same thing, it used to be called VCE on your Vega (more here : https://en.wikipedia.org/wiki/Video_Coding_Engine) but changed name to VCN. Intel iGPU have the same thing with QuickSync which is also a fixed unit. Videos basically never gets decoded by the GPU units.

I've attached an annotated screenshot of where I was getting those GPU usage figures from. iStat Menus. The clock speed reported for the main GPU remains low throughout Aerial playback (like 15-100MHz), even though the "usage percentage" increases the more screens that I add.

Thanks ! Clock speed remaining low 100% means your GPU units (shader cores) aren't working/are idle. I'm not completely sure what that "usage" graphic corresponds to, since the clock is low there's practically no chance that's GPU unit usage (which is hard to gather in any case).
It would seem reasonable to me that this may be GPU memory usage though. And that could definitely explain the difference you see with multiple screens, especially since you run different videos on each screen. VCE is probably caching those videos in the GPU memory and that's the spike you are seeing with 2 screens.
If that's memory, I would assume that if you have 2 displays in Aerial's mirrored mode, you won't see a difference from 1 display since it won't cache the video twice.

@glouel Thanks for your insights and feedback on this.
The fix in my last post, of ejecting the disk containing the system photo library, turned out to be a brief coincidence, I think.
I did get Aerial working with consistent smooth playback by removing all remnants of Aerial, including prefs and caches, and starting over with 1.8.2. (I had had v1.6 installed previously, at one point.) Since then, I've had the photo library mounted, seems to not be an issue.
Once I got it working, I did do some testing to see what the limits of the iMac Pro are with Aerial, if you are curious. I am also curious as to what you think might be happening.
Attached is another annotated screenshot from the iStat Menus data, for reported VEGA 56 "processor usage %", over about an hour.
There is a corresponding screenshot showing "video memory" usage during the same time interval.
TL;DR the iMac Pro seems to be capable of 3x 4K HEVC independent screens/streams. Stutters with 4. VRAM not maxed... think it could be an imposed limitation with VCE on the Vega 56 to 3 streams, or something like that? I know NVENC has a limitation for the consumer chips.
Thanks

The fix in my last post, of ejecting the disk containing the system photo library, turned out to be a brief coincidence, I think.

Ha, our posts crossed it seems.

I did get Aerial working with consistent smooth playback by removing all remnants of Aerial, including prefs and caches, and starting over with 1.8.2. (I had had v1.6 installed previously, at one point.) Since then, I've had the photo library mounted, seems to not be an issue.

This is troubling, well hopefully that fixed it for you but it's possible I have some issue with some old preference. I started moving some preferences around 1.8 to a new format and got rid of some older stuff, off the top of my head I have no idea how that could impact performance (I've had bugs but not of that kind because of that) but you never know.
Please keep monitoring in case it comes back. And I don't know if you happen to use time machine but... any chance you could grab the old preference file before you wiped it and attached it here ? That might be super helpful.

Once I got it working, I did do some testing to see what the limits of the iMac Pro are with Aerial, if you are curious. I am also curious as to what you think might be happening.

Of course!

Attached is another annotated screenshot from the iStat Menus data, for reported VEGA 56 "processor usage %", over about an hour.

So it's processor usage, hmm. I really need to install iStat Menus to see what they exactly measure. The Core clock still being low still implies no usage though, so I'm not sure how to reconcile those, unless they factor UVD/VCE in there.

There is a corresponding screenshot showing "video memory" usage during the same time interval.
TL;DR the iMac Pro seems to be capable of 3x 4K HEVC independent screens/streams. Stutters with 4. VRAM not maxed... think it could be an imposed limitation with VCE on the Vega 56 to 3 streams, or something like that? I know NVENC has a limitation for the consumer chips.

So I'm not 100% sure but off memory, there is a limit to the number of simultaneously decoded streams in most of these fixed units, which may depend on codec and size. I'm curious though when you mean stuttering, were some smooth and one stuttering, all stuttering in sync if you see what I mean ? I would expect 4 screens in mirrored in no issue also ?
It's getting late here so I'll try to dig a bit more into it tomorrow, I'm a bit puzzled by your GPU processor graph, whatever it means, that's hitting 100% as to what that exactly means.
Couple of complementary questions for you:

Are you running 4K HEVC or 4K HDR ? HDR playback implies some amount of tone mapping on non Mac Pros so that may play a factor in this. Both are 10bits encoded in any case (but Vega does 4K HEVC 10bit decoding natively)
Did you try 1080pHEVC to see if 4 screens was doable ? And 1080p H264 ?

Yes, will attach old prefs. When attempting 4 independent 4K HEVC from the VEGA 56, all are mostly stuttering in sync, or the same degree, but one (a 1080 display I had hooked up) was slightly smoother.
Have been selecting the 4K HEVC, non-HDR videos.
Haven't tried any of the 1080p options.
Achieving 4 independent screens is not really something that I need to accomplish currently, though I am curious to see if 3 is some sort of max for this specific AMD chip / iMac Pro.
Yeah, hard to know what iStat Menus is really representing there, with the main clock remaining minimal. (Also thermals aren't drastically shooting up, like when the GPU really is at full tilt.)
I did try doing 'mirrored' in Aerial, across 4 screens, it is totally smooth; iStat reports the same 'VEGA 56 processor usage %' it does as when just running a single monitor. (~30%.)
BTW, on this iMac Pro, I can play a locally stored 4K feature film (Apollo 11, HEVC 10-bit REMUX Blu-ray rip, ~60Mbps average video bitrate) through a media player like IINA or VLC.
When doing this, iStat shows roughly the same "VEGA56 usage %" (~30%) as the presumably lower bitrate Aerial files.
com.JohnCoates.Aerial.C060F294-29ED-5DF9-ABD8-7CE6F032C79F.plist.zip

Yes, will attach old prefs.

Awesome ! I'll see if I can reproduce somehow, will let you know.

When attempting 4 independent 4K HEVC from the VEGA 56, all are mostly stuttering in sync, or the same degree, but one (a 1080 display I had hooked up) was slightly smoother.

Ok. I tried digging a bit but couldn't find precise info on the UVD 7 version that's on Vega. I remember the really early version were limited to 1 then 2 streams so 3 seems probable, although it could be somewhere else in the pipe.

Have been selecting the 4K HEVC, non-HDR videos.
Haven't tried any of the 1080p options.
Achieving 4 independent screens is not really something that I need to accomplish currently, though I am curious to see if 3 is some sort of max for this specific AMD chip / iMac Pro.

If you really want to dig more, you should try using Quicktime player. Aerial uses the exact same API for playback.

Yeah, hard to know what iStat Menus is really representing there, with the main clock remaining minimal. (Also thermals aren't drastically shooting up, like when the GPU really is at full tilt.)

The core clock is the best indicator that nothing is happenning there. I did give a shot to iStat menus and I also see some "gpu processor activity" :

The first one in red was a 4K HDR video, the second one 4K HEVC. In both cases, I get a GPU usage, despite the video being decoded on the CPU on this iMac in both cases (only 1 video/5K screen).
So at that point, whatever that activity is, doesn't really matter. Could be some post processing (tone mapping) that macOS does, or just show the activity at the back of the GPU around compositing/displaying to screens.

I did try doing 'mirrored' in Aerial, across 4 screens, it is totally smooth; iStat reports the same 'VEGA 56 processor usage %' it does as when just running a single monitor. (~30%.)

Sounds about the same amount of usage I get here with 1 video so yeah, give a shot to multiple Quicktime on one screen if you want to dig more into that I guess.

BTW, on this iMac Pro, I can play a locally stored 4K feature film (Apollo 11, HEVC 10-bit REMUX Blu-ray rip, ~60Mbps average video bitrate) through a media player like IINA or VLC.

VLC does have it's own path to hardware acceleration (different than Aerial/Quicktime as in they don't use the Apple's API but go more low level), but even without, one such stream should play fine on pretty much anything. Your CPU can probably decode 3 of those too ;)
And for the fixed unit in your Vega, they don't care much about bitrate (they are tailored to handle the full BR profiles on recent iterations) so it should have 0 impact on them.

When doing this, iStat shows roughly the same "VEGA56 usage %" (~30%) as the presumably lower bitrate Aerial files.

Which makes me think this is either post processing or ROP activity but not decoding.
Thanks for the pref file I'll try to have a look soonish and let me know if the issues comes back or not (one possible thing if it's mediaanalysis is it was done with your stuff, so maybe make a few videos ;)).

Hey,
So, the stuttering-with-multiple-video-streams issue recurred on this iMac Pro running Aerial 1.8.2 and 10.15.4.
Aerial appears to be causing double the GPU usage after initial post-reboot run, making running two displays jerky.
To recap: I have 2 displays. The iMac Pro itself, plus an external Thunderbolt Display; Aerial set to 4K HEVC video format.
After a reboot, before Aerial runs, I can smoothly play up to 3 HEVC streams of a test video in QuickTime Player.
When I look in Activity Monitor, the “GPU %” shows about ~30% usage for each stream that I add.
Once Aerial runs, if I open QuickTime Player, a single of my test streams now takes ~60% GPU and I can only play 1 smoothly until I reboot again.
(Aerial doesn’t run smoothly at all, until I trash the prefs like last time.)
Any ideas?
Thanks!
Eric

On Apr 23, 2020, at 5:48 AM, Guillaume Louel<EMAIL_ADDRESS>wrote:
Yes, will attach old prefs.
Awesome ! I'll see if I can reproduce somehow, will let you know.
When attempting 4 independent 4K HEVC from the VEGA 56, all are mostly stuttering in sync, or the same degree, but one (a 1080 display I had hooked up) was slightly smoother.
Ok. I tried digging a bit but couldn't find precise info on the UVD 7 version that's on Vega. I remember the really early version were limited to 1 then 2 streams so 3 seems probable, although it could be somewhere else in the pipe.
Have been selecting the 4K HEVC, non-HDR videos.
Haven't tried any of the 1080p options.
Achieving 4 independent screens is not really something that I need to accomplish currently, though I am curious to see if 3 is some sort of max for this specific AMD chip / iMac Pro.
If you really want to dig more, you should try using Quicktime player. Aerial uses the exact same API for playback.
Yeah, hard to know what iStat Menus is really representing there, with the main clock remaining minimal. (Also thermals aren't drastically shooting up, like when the GPU really is at full tilt.)
The core clock is the best indicator that nothing is happenning there. I did give a shot to iStat menus and I also see some "gpu processor activity" :
https://user-images.githubusercontent.com/37544189/80099762-498c0a80-856f-11ea-87d4-fcfc2c85fde8.jpg
The first one in red was a 4K HDR video, the second one 4K HEVC. In both cases, I get a GPU usage, despite the video being decoded on the CPU on this iMac in both cases (only 1 video/5K screen).
So at that point, whatever that activity is, doesn't really matter. Could be some post processing (tone mapping) that macOS does, or just show the activity at the back of the GPU around compositing/displaying to screens.
I did try doing 'mirrored' in Aerial, across 4 screens, it is totally smooth; iStat reports the same 'VEGA 56 processor usage %' it does as when just running a single monitor. (~30%.)
Sounds about the same amount of usage I get here with 1 video so yeah, give a shot to multiple Quicktime on one screen if you want to dig more into that I guess.
BTW, on this iMac Pro, I can play a locally stored 4K feature film (Apollo 11, HEVC 10-bit REMUX Blu-ray rip, ~60Mbps average video bitrate) through a media player like IINA or VLC.
VLC does have it's own path to hardware acceleration (different than Aerial/Quicktime as in they don't use the Apple's API but go more low level), but even without, one such stream should play fine on pretty much anything. Your CPU can probably decode 3 of those too ;)
And for the fixed unit in your Vega, they don't care much about bitrate (they are tailored to handle the full BR profiles on recent iterations) so it should have 0 impact on them.
When doing this, iStat shows roughly the same "VEGA56 usage %" (~30%) as the presumably lower bitrate Aerial files.
Which makes me think this is either post processing or ROP activity but not decoding.
Thanks for the pref file I'll try to have a look soonish and let me know if the issues comes back or not (one possible thing if it's mediaanalysis is it was done with your stuff, so maybe make a few videos ;)).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/940#issuecomment-618382705, or unsubscribe https://github.com/notifications/unsubscribe-auth/APJQB3QZGERVNZX477D34F3ROA2IBANCNFSM4K7UIVTA.

UPDATE:
Disconnected the external display, to take it out of the equation.
After running Aerial a few times with just the built-in screen, both Aerial playback and my test HEVC file (in QuickTime Player) start requiring 2x more "GPU %" than normal to play.
Thus making it only possible to play one HEVC file smoothly, because one stream is using ~60% GPU.
If I reboot, HEVC playback in QuickTime Player takes ~30% GPU, like normal, until running Aerial again.
Thanks

On May 10, 2020, at 4:05 PM, Eric Heyneker<EMAIL_ADDRESS>wrote:
Hey,
So, the stuttering-with-multiple-video-streams issue recurred on this iMac Pro running Aerial 1.8.2 and 10.15.4.
Aerial appears to be causing double the GPU usage after initial post-reboot run, making running two displays jerky.
To recap: I have 2 displays. The iMac Pro itself, plus an external Thunderbolt Display; Aerial set to 4K HEVC video format.
After a reboot, before Aerial runs, I can smoothly play up to 3 HEVC streams of a test video in QuickTime Player.
When I look in Activity Monitor, the “GPU %” shows about ~30% usage for each stream that I add.
Once Aerial runs, if I open QuickTime Player, a single of my test streams now takes ~60% GPU and I can only play 1 smoothly until I reboot again.
(Aerial doesn’t run smoothly at all, until I trash the prefs like last time.)
Any ideas?
Thanks!
Eric

On Apr 23, 2020, at 5:48 AM, Guillaume Louel<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Yes, will attach old prefs.
Awesome ! I'll see if I can reproduce somehow, will let you know.
When attempting 4 independent 4K HEVC from the VEGA 56, all are mostly stuttering in sync, or the same degree, but one (a 1080 display I had hooked up) was slightly smoother.
Ok. I tried digging a bit but couldn't find precise info on the UVD 7 version that's on Vega. I remember the really early version were limited to 1 then 2 streams so 3 seems probable, although it could be somewhere else in the pipe.
Have been selecting the 4K HEVC, non-HDR videos.
Haven't tried any of the 1080p options.
Achieving 4 independent screens is not really something that I need to accomplish currently, though I am curious to see if 3 is some sort of max for this specific AMD chip / iMac Pro.
If you really want to dig more, you should try using Quicktime player. Aerial uses the exact same API for playback.
Yeah, hard to know what iStat Menus is really representing there, with the main clock remaining minimal. (Also thermals aren't drastically shooting up, like when the GPU really is at full tilt.)
The core clock is the best indicator that nothing is happenning there. I did give a shot to iStat menus and I also see some "gpu processor activity" :
https://user-images.githubusercontent.com/37544189/80099762-498c0a80-856f-11ea-87d4-fcfc2c85fde8.jpg
The first one in red was a 4K HDR video, the second one 4K HEVC. In both cases, I get a GPU usage, despite the video being decoded on the CPU on this iMac in both cases (only 1 video/5K screen).
So at that point, whatever that activity is, doesn't really matter. Could be some post processing (tone mapping) that macOS does, or just show the activity at the back of the GPU around compositing/displaying to screens.
I did try doing 'mirrored' in Aerial, across 4 screens, it is totally smooth; iStat reports the same 'VEGA 56 processor usage %' it does as when just running a single monitor. (~30%.)
Sounds about the same amount of usage I get here with 1 video so yeah, give a shot to multiple Quicktime on one screen if you want to dig more into that I guess.
BTW, on this iMac Pro, I can play a locally stored 4K feature film (Apollo 11, HEVC 10-bit REMUX Blu-ray rip, ~60Mbps average video bitrate) through a media player like IINA or VLC.
VLC does have it's own path to hardware acceleration (different than Aerial/Quicktime as in they don't use the Apple's API but go more low level), but even without, one such stream should play fine on pretty much anything. Your CPU can probably decode 3 of those too ;)
And for the fixed unit in your Vega, they don't care much about bitrate (they are tailored to handle the full BR profiles on recent iterations) so it should have 0 impact on them.
When doing this, iStat shows roughly the same "VEGA56 usage %" (~30%) as the presumably lower bitrate Aerial files.
Which makes me think this is either post processing or ROP activity but not decoding.
Thanks for the pref file I'll try to have a look soonish and let me know if the issues comes back or not (one possible thing if it's mediaanalysis is it was done with your stuff, so maybe make a few videos ;)).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/940#issuecomment-618382705, or unsubscribe https://github.com/notifications/unsubscribe-auth/APJQB3QZGERVNZX477D34F3ROA2IBANCNFSM4K7UIVTA.

Hi @teleport9000
The only thing I can say is that it looks like an API bug from Apple.
By itself Aerial just uses AVPlayer to play videos, and doesn't do anything particularly magical. It has no access to the GPU, the API handles everything and Aerial has about 0 control on all of this . There are some calls that can let you specify a GPU but that part of the API doesn't seem to work. Actually, I just had a look and they updated their documentation with this info : Important
You must specify an external GPU (or a slotted GPU in Mac Pro) with this property. You can’t switch decoding between the integrated graphics and the built-in discrete graphics.
https://developer.apple.com/documentation/avfoundation/avplayer/2942616-preferredvideodecodergpuregistry
I guess that explains why I couldn't get it to work ;) I can't even disable hardware acceleration for you, to give you an idea of how little control I have in all this.
So there's not much I can do except suggest you send a report to Apple via Feedback Assistant, this may prove helpful for them to debug the issue. Sorry that I can't do more on this.

@teleport9000 sorry if I sounded unhelpful yesterday, I did think of one more thing this morning :  most of the time (if not all), a change made with screensavers and Catalina is that they get violently SIGKILLed by the OS without warning. In the pre Catalina days, we were warned that we were going to get killed and Aerial has some code to close the video player to free up ressources if any (again, with Swift, it's completely out of the developer control). It's quite likely that by getting SIGKILLed, some GPU ressources on some systems (like yours) may end up not being freed (whatever those are, for some reason I'm still thinking VRAM despite what the monitoring tool said).
So here's a suggestion that may help you reproduce the issue outside of Aerial:

Launch a video playback with QuickTime Player
In a terminal, try this command : ps aux | grep -i Player

You should get a couple of lines like this :
glouel           20217   0,0  0,2  4906980  31628   ??  S     2:04     0:00.29 /System/Applications/QuickTime Player.app/Contents/MacOS/QuickTime Player

Find the line with QuickTime Player and note the first number after your user account. That's the PID (process id). Then do this in terminal : kill -9 20217 (using the correct number above instead of 20217 ;) )

Then open QuickTime Player again and try again to see if you also see a ressource spike ?

If you do, I would suggest filing a bug report to Apple via Feedback Assistant with both this test case, and an explanation of how this happens too with your screensaver, feel free to point them to this thread. It's likely that this is a GPU/driver specific issue so having your exact hardware/driver configuration (as they do when you use that assistant) will help them troubleshoot it.

Hey,
Thanks for the reply.
I did try "kill -9"ing QuickTime Player a few times. Resource usage seemed normal after (ie when starting playback again).
I was successful in resolving the issue temporarily, by trashing the Aerial prefs.
I’m not sure if it’s helpful, but I’ve attached said prefs (that were in place when it was stuttering).
Thanks,
Eric

On May 11, 2020, at 5:15 AM, Guillaume Louel<EMAIL_ADDRESS>wrote:
@teleport9000 https://github.com/teleport9000 sorry if I sounded unhelpful yesterday, I did think of one more thing this morning : most of the time (if not all), a change made with screensavers and Catalina is that they get violently SIGKILLed by the OS without warning. In the pre Catalina days, we were warned that we were going to get killed and Aerial has some code to close the video player to free up ressources if any (again, with Swift, it's completely out of the developer control). It's quite likely that by getting SIGKILLed, some GPU ressources on some systems (like yours) may end up not being freed (whatever those are, for some reason I'm still thinking VRAM despite what the monitoring tool said).
So here's a suggestion that may help you reproduce the issue outside of Aerial:
Launch a video playback with QuickTime Player
In a terminal, try this command : ps aux | grep -i Player
You should get a couple of lines like this :
glouel           20217   0,0  0,2  4906980  31628   ??  S     2:04     0:00.29 /System/Applications/QuickTime Player.app/Contents/MacOS/QuickTime Player
Find the line with QuickTime Player and note the first number after your user account. That's the PID (process id). Then do this in terminal : kill -9 20217 (using the correct number above instead of 20217 ;) )
Then open QuickTime Player again and try again to see if you also see a ressource spike ?
If you do, I would suggest filing a bug report to Apple via Feedback Assistant with both this test case, and an explanation of how this happens too with your screensaver, feel free to point them to this thread. It's likely that this is a GPU/driver specific issue so having your exact hardware/driver configuration (as they do when you use that assistant) will help them troubleshoot it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/940#issuecomment-626664687, or unsubscribe https://github.com/notifications/unsubscribe-auth/APJQB3RHB2R3T7KHXK3C5T3RQ7T5JANCNFSM4K7UIVTA.

@teleport9000 sorry for the late reply, but can you let me know if deleting the preferences again solved it durably for you ?

Hi,
Yes, it has continued to work, thanks.
It did take roughly two weeks for the issue to recur last time.
I just looked at the calendar, it has been exactly two weeks since I trashed the prefs.
I’ll keep you posted if it recurs.
Thanks

On May 24, 2020, at 9:46 AM, Guillaume Louel<EMAIL_ADDRESS>wrote:
@teleport9000 https://github.com/teleport9000 sorry for the late reply, but can you let me know if deleting the preferences again solved it durably for you ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/940#issuecomment-633258470, or unsubscribe https://github.com/notifications/unsubscribe-auth/APJQB3VQP4XJB5NEAPLN3CDRTFFM5ANCNFSM4K7UIVTA.

Hey @glouel , I know you've addressed this but I can’t seem to find a fix...
High CPU usage/fan spinning all of a sudden: If you correctly configured the preferred video format according to your Mac and still experience high CPU usage/fan spinning all of a sudden, please look for the cause with Activity Monitor, you may see a com.apple.photos.ImageConversionService responsible for this CPU load. This is the iCloud Photos process, you can find more about what it does here and how to pause it.
The link doesn't seem to provide any useful insight on how to disable, i think it's since been changed. I am trying to run 4k HDR video, I know in SDR I don’t have this issue.
Mac model: MacBook Pro 15-inch 2015
macOS version: macOS Catalina 10.15.35
Monitor setup: TV via HDMI in clamshell (Radeon Pro 560X 4 GB graphics)
Let me know if you can help.

Hi @jonfoxnj

I am trying to run 4k HDR video, I know in SDR I don’t have this issue.
Mac model: MacBook Pro 15-inch 2015

So, in your case I think the issue is more simple, 2015 macs don't have full support for hardware decoding of those videos. So because of this, the video must be decoded by the CPU so it may stutter or spin your fan.
There's a help bubble next to where you pick the video format, I suggest you click it :

There's a (not 100% but reliable) test at the bottom of the screen that tells you if you can play HEVC videos or not (with extra explanation). In your case, depending on whether it's an early or late 2015, it will either be red or yellow I think. In general, only 2017+ Macs can use GPU decoding (and thus no fan spinning and minimal power consumption) for 4K/HDR.
To double check you can try opening one of the 4K HDR videos with Quicktime (you can go into Aerial's cache tab to access the folder where the videos are stored, you will probably see exactly the same thing as you see with Aerial (I use the exact same APIs).
So not a lot you can do here on this laptop but go back to a lower setting.

Jon Fox
(201) 248-8573
<EMAIL_ADDRESS>
On May 27, 2020, at 2:17 PM, Guillaume Louel<EMAIL_ADDRESS>wrote:
Hi @jonfoxnj https://github.com/jonfoxnj
I am trying to run 4k HDR video, I know in SDR I don’t have this issue.
Mac model: MacBook Pro 15-inch 2015
So, in your case I think the issue is more simple, 2015 macs don't have full support for hardware decoding of those videos. So because of this, the video must be decoded by the CPU so it may stutter or spin your fan.
There's a help bubble next to where you pick the video format, I suggest you click it :
https://user-images.githubusercontent.com/37544189/83056851-6035ed80-a056-11ea-82c2-820d0cb7771c.jpg
There's a (not 100% but reliable) test at the bottom of the screen that tells you if you can play HEVC videos or not (with extra explanation). In your case, depending on whether it's an early or late 2015, it will either be red or yellow I think. In general, only 2017+ Macs can use GPU decoding (and thus no fan spinning and minimal power consumption) for 4K/HDR.
To double check you can try opening one of the 4K HDR videos with Quicktime (you can go into Aerial's cache tab to access the folder where the videos are stored, you will probably see exactly the same thing as you see with Aerial (I use the exact same APIs).
So not a lot you can do here on this laptop but go back to a lower setting.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/940#issuecomment-634850124, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFHQKRY3MPDSMYK4O3XY4ZTRTVKKXANCNFSM4K7UIVTA.

Here’s the confirmation screenshot as well.
Jon Fox
(201) 248-8573
<EMAIL_ADDRESS>
On May 27, 2020, at 2:17 PM, Guillaume Louel<EMAIL_ADDRESS>wrote:
Hi @jonfoxnj https://github.com/jonfoxnj
I am trying to run 4k HDR video, I know in SDR I don’t have this issue.
Mac model: MacBook Pro 15-inch 2015
So, in your case I think the issue is more simple, 2015 macs don't have full support for hardware decoding of those videos. So because of this, the video must be decoded by the CPU so it may stutter or spin your fan.
There's a help bubble next to where you pick the video format, I suggest you click it :
https://user-images.githubusercontent.com/37544189/83056851-6035ed80-a056-11ea-82c2-820d0cb7771c.jpg
There's a (not 100% but reliable) test at the bottom of the screen that tells you if you can play HEVC videos or not (with extra explanation). In your case, depending on whether it's an early or late 2015, it will either be red or yellow I think. In general, only 2017+ Macs can use GPU decoding (and thus no fan spinning and minimal power consumption) for 4K/HDR.
To double check you can try opening one of the 4K HDR videos with Quicktime (you can go into Aerial's cache tab to access the folder where the videos are stored, you will probably see exactly the same thing as you see with Aerial (I use the exact same APIs).
So not a lot you can do here on this laptop but go back to a lower setting.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/JohnCoates/Aerial/issues/940#issuecomment-634850124, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFHQKRY3MPDSMYK4O3XY4ZTRTVKKXANCNFSM4K7UIVTA.

Ha, no worries. So yep it might be the other thing. You didn't tell me, does it happen 100% of the time or some of the time ?
I'll have a look in an hour or so and get back to you, thanks.

Happens 100% of the time. Yea sounds good thanks for the time!

@jonfoxnj please go to this issue : https://github.com/JohnCoates/Aerial/issues/999
I split it so we can separate your issue which look different. Thanks!

Hi,
The stuttering issue came back on this iMac Pro (when using more than one display).
Too many possible factors this time:
-time-up on the mysterious ~2 week durability observed so far?
-upgraded to 10.15.5
-upgraded to 1.9.0
It is working for now, with new fresh prefs.
I am attaching the "corrupted" prefs along with the "fresh" ones, that I just set up (2nd file).
Thanks!
Eric
Link to prefs:
https://bearcrusher.duckdns.org:5001/sharing/AdFalpwn2

Hi, Yes, it has continued to work, thanks. It did take roughly two weeks for the issue to recur last time. I just looked at the calendar, it has been exactly two weeks since I trashed the prefs. I’ll keep you posted if it recurs. Thanks
…
On May 24, 2020, at 9:46 AM, Guillaume Louel @.***> wrote: @teleport9000 https://github.com/teleport9000 sorry for the late reply, but can you let me know if deleting the preferences again solved it durably for you ? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#940 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APJQB3VQP4XJB5NEAPLN3CDRTFFM5ANCNFSM4K7UIVTA.

Ok this is crazy, I grabbed your two preferences files and will have a look tomorrow and let you know !

Great.
Thanks so much for your time, etc. with this.
I love staring at these.
Eric

Lol I'll admit I love staring at these too, really appreciate the time and effort you've put into this.

Hey there,
I have the same Issues did a clean install etc. nothing special on my iMac Pro and getting stutter as soon as the new Big Sur Screensaver starts, when playing back HEVC 4K Content.
I noticed, that the Radeon 56 Vega won't clock up, staying at 14-26MHZ.
I have an iMac Pro 2017, 32GB Ram, 1TB SSD and Radeon 56.
after reboot problem disappears. so what could that really be? I think its something like a Power-State Bug happening on the GPU?!

Hey there,
I have the same Issues did a clean install etc. nothing special on my iMac Pro and getting stutter as soon as the new Big Sur Screensaver starts, when playing back HEVC 4K Content.
I noticed, that the Radeon 56 Vega won't clock up, staying at 14-26MHZ.
I have an iMac Pro 2017, 32GB Ram, 1TB SSD and Radeon 56.
after reboot problem disappears. so what could that really be? I think its something like a Power-State Bug happening on the GPU?!

Hey @raveya
Did you check the clock when it plays normally ? Decoding is done on a fixed unit so the clock isn't really indicative of decoding, but there's a tiny bit of GPU activity for the actual displaying of the video etc on 4K HEVC (there's more on HDR). With that said it should be 100% smooth for you.
Considering rebooting helps, and nothing "stays around" from one launch of Aerial to the other, this is perplexing. Next time you hit the bug, could you try opening one of Aerial's video in quicktime just to see if it lags there too ?
My quick guess is this is probably a graphics driver bug but any data may be useful. Thanks !


Unable to create bridge on same subnet of VF

I tried to create to the bridge using sriov plugin but it kept on failing on ROCE CX5 card. I tried to use the same subnet which is available on host devices i.e. <IP_ADDRESS>/24 but I get following error:
docker network create -d sriov --subnet=<IP_ADDRESS>/24 -o netdevice=re6 -o mode=passthrough mynet1   Error response from daemon: Pool overlaps with other one on this address space
I am able to create the bridge if I use different subnet but for my usecase bridge must be on same subnet so that I can reach other nodes running on same subnet.  Also, I want to know if rdma stack can work inside the container? will rds-ping will work inside the container?

@psaini79

mode should be sriov. mode=sriov.
rds-pring won't work, as its unsupported currently.
other application such as rping should work depending on which kernel version you are running. kernel 4.19/4.20 is required for RoCE.
This plugin doesn't create any bridge.
You can have your PF netdevice in same subnet as that of container VFs.

Here is a sample example,
ifconfig ens1f0
ens1f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
inet6 fe80::268a:7ff:fe55:4660  prefixlen 64  scopeid 0x20
ether 24:8a:07:55:46:60  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 8  bytes 648 (648.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
$ docker network create -d sriov --subnet=<IP_ADDRESS>/24 -o netdevice=ens1f0 mynet
This will allow you to reach to other nodes in same subnet on other systems or VF to PF communication too.

Thanks for the quick reply. I tried to create the network using SRIOV on same subnet  but it didn't work.
 ifconfig re1 re1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2300         inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>         ether 50:6b:4b:df:17:1f  txqueuelen 1000  (Ethernet)         RX packets 24737  bytes 1706634 (1.6 MiB)         RX errors 1692  dropped 0  overruns 0  frame 1692         TX packets 6911  bytes 465960 (455.0 KiB)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
docker network create -d sriov --subnet=<IP_ADDRESS>/24 -o netdevice=re1 mynet Error response from daemon: Pool overlaps with other one on this address space
Kernel version on host:
uname -a Linux scaqaj01adm02.us.oracle.com 4.14.35-1902.0.12.el7uek.x86_64 #2 SMP Sat Mar 23 10:27:18 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
Kernel version on Container
uname -a Linux racnode6 4.14.35-1902.0.12.el7uek.x86_64 #2 SMP Sat Mar 23 10:27:18 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux
So rdma stack is supported from kernel version 4.19 inside the container?  I am asking this question because when I create a macvlan bridge on ROCE interface and assign to container , I am able to ping all other IPs but /proc/sys/net/rds doesn't appear inside the container so rds-ping fails. I understand rds-ping is not supported but rping can work and rdma can be supported for ROCE from 4.19?
lspci output
`
lspci | grep Mel
54:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
54:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
54:03.2 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:03.3 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:03.4 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:03.5 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:03.6 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:03.7 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:04.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:04.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:04.2 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:04.3 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:04.4 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:04.5 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:04.6 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:04.7 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:05.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:05.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:05.2 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:05.3 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:05.4 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:05.5 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:05.6 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:05.7 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:06.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
54:06.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex Virtual Function]
74:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
74:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
94:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
94:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
b4:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
b4:00.1 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5 Ex]
`
ifconfig output
`
ifconfig
bondeth0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether b0:26:28:2f:42:00  txqueuelen 1000  (Ethernet)
RX packets 1941744  bytes<PHONE_NUMBER> (2.0 GiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 497208  bytes 59359447 (56.6 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 02:42:7f:c0:04:da  txqueuelen 0  (Ethernet)
RX packets 129235  bytes 6897362 (6.5 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 302056  bytes 505027213 (481.6 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet <IP_ADDRESS>  netmask <IP_ADDRESS>
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 297267  bytes 30985391 (29.5 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 297267  bytes 30985391 (29.5 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
lo:1: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet <IP_ADDRESS>  netmask <IP_ADDRESS>
loop  txqueuelen 1000  (Local Loopback)
lo:2: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet <IP_ADDRESS>  netmask <IP_ADDRESS>
loop  txqueuelen 1000  (Local Loopback)
lo:3: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet <IP_ADDRESS>  netmask <IP_ADDRESS>
loop  txqueuelen 1000  (Local Loopback)
re0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2300
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 50:6b:4b:df:17:1e  txqueuelen 1000  (Ethernet)
RX packets 30956  bytes 2173450 (2.0 MiB)
RX errors 514  dropped 0  overruns 0  frame 514
TX packets 12153  bytes 874026 (853.5 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
re1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2300
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 50:6b:4b:df:17:1f  txqueuelen 1000  (Ethernet)
RX packets 24762  bytes 1708514 (1.6 MiB)
RX errors 1692  dropped 0  overruns 0  frame 1692
TX packets 6936  bytes 467840 (456.8 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
re2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2300
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 50:6b:4b:df:17:26  txqueuelen 1000  (Ethernet)
RX packets 28286  bytes 1919878 (1.8 MiB)
RX errors 514  dropped 0  overruns 0  frame 514
TX packets 9786  bytes 637700 (622.7 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
re3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2300
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 50:6b:4b:df:17:27  txqueuelen 1000  (Ethernet)
RX packets 23159  bytes 1589838 (1.5 MiB)
RX errors 1690  dropped 0  overruns 0  frame 1690
TX packets 5559  bytes 362762 (354.2 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
re4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2300
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 50:6b:4b:df:17:2e  txqueuelen 1000  (Ethernet)
RX packets 39767  bytes 2586470 (2.4 MiB)
RX errors 514  dropped 0  overruns 0  frame 514
TX packets 61958  bytes 5282890 (5.0 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
re5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2300
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 50:6b:4b:df:17:2f  txqueuelen 1000  (Ethernet)
RX packets 30595  bytes 2169872 (2.0 MiB)
RX errors 1690  dropped 0  overruns 0  frame 1690
TX packets 11031  bytes 738886 (721.5 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
re6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2300
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 50:6b:4b:df:17:16  txqueuelen 1000  (Ethernet)
RX packets 26861  bytes 1834644 (1.7 MiB)
RX errors 514  dropped 0  overruns 0  frame 514
TX packets 9953  bytes 652546 (637.2 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
re7: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2300
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 50:6b:4b:df:17:17  txqueuelen 1000  (Ethernet)
RX packets 29980  bytes 2132858 (2.0 MiB)
RX errors 1690  dropped 0  overruns 0  frame 1690
TX packets 11153  bytes 749550 (731.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
ether 52:54:00:e6:d3:af  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
`

@psaini79 @psaini2018
I just checked patches, kernel 4.20 or higher is required.
yes, rping and rdma should work.
You  should follow this post.
Not too much different than what you are doing. Just for the reference.
https://community.mellanox.com/s/article/docker-rdma-sriov-networking-with-connectx4-connectx5
for duplicate subnet IP, please share the docker version and sriov plugin logs.
I suspect you have these issue because you have multiple netdevices in same subnet.
And this is not an issue with the sriov plugin. It seems to be a failure from the docker.

Thanks, you are right. I am able to create network on same subnet and able to ping the target from container.
[root@b1936cddf1d3 mofed_installer]# ifconfig eth0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500         inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>         ether 8e:d4:4b:dc:dd:dd  txqueuelen 1000  (Ethernet)         RX packets 5  bytes 376 (376.0 B)         RX errors 0  dropped 0  overruns 0  frame 0         TX packets 5  bytes 376 (376.0 B)         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
ping command to target works
[root@b1936cddf1d3 mofed_installer]# ping <IP_ADDRESS> PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data. 64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=64 time=0.120 ms 64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=64 time=0.078 ms
However, rping command is failing. I executed following command on server i.e. on <IP_ADDRESS>:
 rping -s -C -a <IP_ADDRESS> -v
Executed following command inside the container:
[root@b1936cddf1d3 mofed_installer]# rping -c -a <IP_ADDRESS> -v cma event RDMA_CM_EVENT_ADDR_ERROR, error -19 waiting for addr/route resolution state 1
I created the container using following command:
 docker_rdma_sriov run --net=mynet --ip=<IP_ADDRESS> -it mellanox/mlnx_ofed_linux-4.4-<IP_ADDRESS>-centos7.4 bash

@psaini79
Can you please share the output when running rping -d ...
We also likely need to see kernel ftraces if it doesn't work.
We haven't tried mofed user space and upstream kernel.
Usually with upstream kernel, upstream rdma-core (any version) should be used.
With mofed kernel, mofed user space should be used.
So post this, you might want to create rdma-core based container image.
Please also share the docker run command that you run.
Did you follow the post I shared previously, listed below?
https://community.mellanox.com/s/article/docker-rdma-sriov-networking-with-connectx4-connectx5

Yes, I followed the steps given in https://community.mellanox.com/s/article/docker-rdma-sriov-networking-with-connectx4-connectx5. However, I executed steps from 5th step onward. Also, following commands exit the container without any error:
docker run --net=host -v /usr/bin:/tmp rdma/container_tools_installer
Please find the output of rping -d below:
`
[root@b1936cddf1d3 mofed_installer]# rping -d -c -a <IP_ADDRESS> -v
client
verbose
created cm_id 0x97f1c0
cma_event type RDMA_CM_EVENT_ADDR_ERROR cma_id 0x97f1c0 (parent)
cma event RDMA_CM_EVENT_ADDR_ERROR, error -19
waiting for addr/route resolution state 1
destroy cm_id 0x97f1c0
`
I have one more question, any ETA for rds_ping to work inside the container?

@psaini2018
please share output of
$ ibdev2netdev in container
$ show_gids in container
$ uname -a on host.
What is the command you ran to run this container?
Please talk to Mellanox support for rds-ping.

The above command failed inside the container:
[root@9098b076cc9a mofed_installer]# ibdev2netdev
bash: ibdev2netdev: command not found
[root@9098b076cc9a mofed_installer]# show_gids
bash: show_gids: command not found
uname -a
Linux rdma-setup 4.14.35-1902.0.12.el7uek.x86_64 #2 SMP Sat Mar 23 10:27:18 PDT 2019 x86_64 x86_64 x86_64 GNU/Linux

@psaini2018 so as we discussed yesterday in this thread that you need kernel 4.20. Please upgrade to it.

I need to upgrade the host kernel to 4.20? Just want to make sure to avoid any rework. Also, for rds_ping SR need to be opened through MLX support login? or is there any github repo for that to open the issue?

@psaini2018, yes 4.20 or higher. 5.1 is even better. :-)
rds-ping is owned by Oracle, you should first resolve at Oracle on supporting rds-ping before opening Mellanox support case.

Ok and thanks a lot for your quick reply.
As per the following link Ethernet card inside the container made available using IPoIB.
https://community.mellanox.com/s/article/docker-rdma-sriov-networking-with-connectx4-connectx5
I have a question, what is the difference between IPoIB device and VM IPoIB device? are they technically same?

@psaini2018
yes.
Can you please close this issue?
If you like the plugin you can also star it. :-)