Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

catch lies [ too much recursion error ] #51

Open
serzz1990 opened this issue Feb 14, 2022 · 6 comments
Open

catch lies [ too much recursion error ] #51

serzz1990 opened this issue Feb 14, 2022 · 6 comments

Comments

@serzz1990
Copy link

my config is 1 in 1 with: https://github.com/kkoooqq/fakebrowser#-demo1-quick-start

open: https://abrahamjuliot.github.io/creepjs/

catch lies:

  • failed at too much recursion error
  • failed at too much recursion proto error
  • failed at chain cycle proto error
  • failed at reflect set proto
  • failed at instanceof check error
@serzz1990
Copy link
Author

in the incogniton browser I did not find such problems. https://incogniton.com/
I opened the source code, and there goes the usual replacement through Object.defineProperty without Proxy.

@serzz1990
Copy link
Author

sorry for my English :)

@dstampher
Copy link

Also having this exact same issue when using CreepJS to test my browser fingerprint. Trying to run the demo. :) I am using Chrome Version 98.0.4758.102 (Official Build) (64-bit) as the executable. Do I need to use an older version of Chrome?

@Somberor
Copy link

Author

So you was able to solve the issue by Object.defineProperty?

@serzz1990
Copy link
Author

Author

So you was able to solve the issue by Object.defineProperty?

I came to the conclusion that it is necessary to make overrides at the highest level, namely in chrome itself. i created a repository to solve this problem.
I have already managed to override some of the properties of the navigator and screen, you only need to pass special flags . more here

@Iquaridys
Copy link

Author

So you was able to solve the issue by Object.defineProperty?

I came to the conclusion that it is necessary to make overrides at the highest level, namely in chrome itself. i created a repository to solve this problem. I have already managed to override some of the properties of the navigator and screen, you only need to pass special flags . more here

I saw your project, I'm interested I hope you can complete it. Unfortunately I'm a windows user

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants