Page 2 of 2

Re: Custom Scheme Handler doesn't read full response

PostPosted: Wed Jul 08, 2020 7:06 pm
by shannah
I don't see a directory named "swiftshader". Where should be be located?

Also, has anything changed in the required structure since these directions:
https://bitbucket.org/chromiumembedded/ ... t-56293671

Re: Custom Scheme Handler doesn't read full response

PostPosted: Wed Jul 08, 2020 8:48 pm
by magreenblatt
Ah, you’re on macOS. Then there’s no swiftshader folder. See the README.txt file in the CEF binary directory for required binaries.

Re: Custom Scheme Handler doesn't read full response

PostPosted: Thu Jul 09, 2020 10:30 am
by shannah
I think it's all there. If I remove the --disable-gpu flag from the args it removes that error message - but it is still sluggish. I'm reverting to the previous version for now (May 21st) as the new version didn't fix the scheme handler issue, and it caused fairly significant performance regressions.

Re: Custom Scheme Handler doesn't read full response

PostPosted: Thu Jul 09, 2020 10:39 am
by shannah
Actually... I'll roll back a little bit on the performance degradation statement. I was doing a debug build. When I switched to a release build, the performance improved somewhat... I'm not sure it if it brings it all the way back, but it's close enough that it's not an obvious performance regression.

Re: Custom Scheme Handler doesn't read full response

PostPosted: Thu Jul 09, 2020 11:16 am
by shannah
Here is a minimal example of the modified ClientSchemeHandler to return a sample MP3 file to demonstrate the problem.
https://gist.github.com/shannah/6340312 ... 42ff79845a

In this case it only calls readResponse() twice, then it starts playing the beginning of the audio file, but stops playing when it reaches the end of what had been loaded with readResponse.
This is using

JCEF Version = 83.4.0.259
[java] [java] CEF Version = 83.4.0
[java] [java] Chromium Version = 83.0.4103.106

Re: Custom Scheme Handler doesn't read full response

PostPosted: Wed Jul 15, 2020 12:29 pm
by shannah
Note: I was able to get this working by ditching the custom scheme approach and using a ResourceHandler instead with an https URL.