BrowserAutomationStudio 21.9.0 has been released



  • Reworked canvas changing mechanism.

    The method by which canvas fingerprint is changed has been significantly improved. This is done to prevent antidetect systems from detecting fingerprint change. This changes includes a whole set of measures, here is only one example - instead of replacing the color for each pixel, the whole image is now analyzed, its outlines are located, finally pixel colors are changed only "on the border":

    0_1560242007533_2019-06-10_21-01-09.gif

    Borders on the image above is highlighted with red color.

    This allows you to pass browser tests with positive results:

    https://i.imgur.com/e4ezKSQ.png

    (navigator test gives a false positive result also in a normal browser, dns depends on the proxy).

    Also, I added some of my tests to validate canvas integrity:

    https://fingerprints.bablosoft.com/canvas

    Canvas changing now works with the alpha channel.

    This means that if canvas contains a black and white image, browser fingerprint will still change.

    The new BAS version draws browser content using GPU for rendering.

    The old implementation used only CPU, but this approach can be detected. You can revert to the previous rendering method by replacing the values

    --disable-gpu-deleted
    --disable-gpu-compositing-deleted
    

    to

    --disable-gpu
    --disable-gpu-compositing
    

    In chrome_command_line.txt file

    https://i.imgur.com/Rdayf97.png

    CPU usage while changing fingerprints has been significally decreased.

    BAS does not slow down when visiting sites that work intensively with graphics, such as streaming services.

    Added a new factor for FingerprintSwitcher: ClientRectangles.

    This method allows you to get device fingerprint by obtaining the size of a specially composed elements. Unlike canvas, only the width, height, and coordinates are analyzed, not the colors of each pixel. These values are platform-dependent and can be used to compose fingerprints. After update BAS adds noise to them, big enough to change the fingerprint, but not too big to break site functionality.

    You can test it here:

    https://browserleaks.com/rects

    Fixed date change issues when using daylight saving time.

    The date is calculated according to the current rules of daylight saving time in the country and region where the ip is located.

    https://i.imgur.com/DV2m9rU.png

    Here is a simple test that shows whether there is a daylight saving time in your country or region. It does not depend on the current date, and it is a good place to check whether your fingerprint change system can replace system date correctly:

    https://jsfiddle.net/jp6rkcs4/

    Added ability to merge FingerprintSwitcher keys and buy keys without ip bindings.

    These opportunities will appear in a few days.

    Task scheduler has been updated.

    The new 1.2.0 version contains a redesigned mechanism to interrupt tasks. Any task will be stopped instantly, no matter at what stage of execution or installation it was.

    The scheduler will not be updated automatically. You need to agree to update it, because all tasks must be stopped during scheduler update.

    https://i.imgur.com/v1OFd4i.png

    "Ignore errors" block will catch errors when executing javascript.

    These can be: JSON parsing errors, nonexistent variables, etc.

    https://i.imgur.com/rwv1xAm.png

    Native combobox are now supported.

    0_1560242057577_2019-06-10_17-24-06.gif

    However, it is still necessary to automate the selection of an element in the old way. This change will be very useful for use in manual mode.

    And many other changes:

    • The site domain is now obtained through a proxy when using the http client.
    • Fixed errors when working with nested loops for elements.
    • Removed mention of BAS from logs and other files of compiled scripts.
    • Fixed issues when working with database and column date type.
    • Any errors without block "Ignore errors" in OnApplicationStart will stop application.
    • When you select an alternative server for the captcha solving, BAS automatically adds a slash to the server url.
    • If you use negative coordinates to move the mouse, events about moving the mouse off the screen will be automatically triggered.
    • Fixed issues with visibility events of the browser in the web interface.


  • @support on 20 browser instances in same time, difference between 2.1.9.0 and previous version in cpu usage is humongous.

    previous version, same bot: 30-60% CPU usage, no lags on pc, very low or 0% GPU usage
    21.9.0 version, 20% GPU usage, 99% CPU usage !! total lagfest. i have fast pc and 6th generation i7. shouldnt be a a problem with 20 browser instances.

    I fixed it with:
    --disable-gpu
    --disable-gpu-compositing

    and it started working correctly



  • @yourfriendkarol Investigating high CPU usage, meanwhile I strongly advise against disabling GPU rendering.



  • Nice, But how can I change
    0_1560340625935_2b6b2a04-ff9a-45ee-851c-936774579f59-image.png
    It still has a BAS icon.

    Also on debug can you add features to make it random Folder Name instead of these folders
    0_1560340856381_490a68d8-88e6-4ccf-aa15-13afb059ca3b-image.png

    Also if you can add an option to compile without debug file it will be better (Checkbox).

    Thanks



  • @support , in 21.9.2 this is default chrome_command_line.txt file or is it caused because i had it in previous version set like this?

    --disable-gpu
    --disable-gpu-compositing
    --disable-gpu-shader-disk-cache
    --enable-widevine-cdm
    

    Thats what I have after update.

    Should I set:
    --disable-gpu-deleted
    --disable-gpu-compositing-deleted

    As your recommended before?
    I want to turn ON gpu rendering



  • @yourfriendkarol It is default now. It turn out that CEF(framework to control browser which BAS uses) doesn't work well in GPU mode and it is known problem.
    In the same time, empty image obtained from canvas with WebGL content (bug that made me move to webgl render) was fixed in 70 Chrome version, so Chrome version was updated and problem disappeared.



  • @support said in BrowserAutomationStudio 21.9.0 has been released:

    @yourfriendkarol It is default now. It turn out that CEF(framework to control browser which BAS uses) doesn't work well in GPU mode and it is known problem.
    In the same time, empty image obtained from canvas with WebGL content (bug that made me move to webgl render) was fixed in 70 Chrome version, so Chrome version was updated and problem disappeared.

    alt text

    it doesnt show any gpu usage on workers



  • @yourfriendkarol Yes, that is expected behaviour


Log in to reply