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
recursion testing #1789
Comments
Fedora 39; x86_64; Firefox 121 (from Fedora); baselinejit,ion=false; |
i'm updating OP with results as I go |
Arch Linux; 64 bit; Firefox 121.0-1; javascript.options.baselinejit=false javascript.options.baselinejit=true:
|
Firefox 121.0 (64-bit) running on Windows 10 22H2 (32.0 GB of RAM). Firefox is running on default settings (javascript.options.baselinejit = true)
level: 11788 Thanks |
@iam-py-test I don't think your worker result for baselinejit = true is correct |
Sorry
Wonder why it didn't work the first time... |
it worked the first time, my test page is a bit shit to copy paste - i,e you can't do it in one hit - so its just a copy/past human error |
Added javascript.options.baselinejit=true to my post |
so far this is promising ... android, mac intel, arm (IDK if I'm using the right words! 😁 ) might tell a different story - so far it's looking like equivalency of items that can't really be masked - so the only issue here is likely to be that the pref state on startup can be detected as a bit of information which would add entropy when the user changes the security slider to be the opposite during a session (but I have a cunning plan to fix that) |
WORKER DOCUMENT IFRAME LMDE6, x64, Firefox 121 mint-001 -1.0, javascript.options.baselinejit = true WORKER DOCUMENT IFRAME LMDE6, x64, Firefox 121 mint-001 -1.0, javascript.options.baselinejit = false LMDE6 is basically Debian 12 Bookworm and I see you already got results for that but I still wanted to add to this. EDIT - Here's TB as well if you want: WORKER DOCUMENT IFRAME LMDE6, x64, Tor Browser 13.0.8, javascript.options.baselinejit = false WORKER DOCUMENT IFRAME LMDE6, x64, Tor Browser 13.0.8, javascript.options.baselinejit = true |
System: MacBook Pro (16-inch, 2021)
Results: https://arkenfox.github.io/TZP/tests/recursion.html
System: Google Pixel 7 Pro
Results: https://arkenfox.github.io/TZP/tests/recursion.html
|
@g-2-s re |
@javulticat those are great, thanks, except the results have true = false. You need to restart firefox in between tests (on android I use menu>quit - I didn't need to force quit from apps) |
I ran the test again to make sure, still the same result, pic for proof: |
@Thorin-Oakenpants I triple-checked my results after changing the config option using a variety of ways to exit and restart the browser (quit normally, force quit and clear cache, restart OS - each time confirming in Perhaps this behavior is somehow specific to AArch64 architectures, since I am seeing the same thing on two systems based on that architecture family? Or perhaps my config is enabling/disabling other settings that are causing any change to Another thing that may be rather unique about my systems is that macOS on Apple silicon is 64-bit-only (from CPU to OS to apps) and the Pixel 7/7 Pro were the first ever 64-bit-only Android phones (likewise, from CPU to OS to apps), despite the fact that 32-bit instruction sets can be enabled on AArch64 chips (and are enabled on almost every other mobile SoC - AFAIK, the Google Fold and Pixel 7a/8/8 Pro, all also based on the Google Tensor G2/G3 SoC, are the only other 64-bit-only Android phones on the market so far). The only other entry in your list that looks like it may also be from a 64-bit-only AArch64-based system is the M1 iMac (they still make iMacs?), but its results look rather suspect to me, as its I will try the test on my x86_64 Windows 11 machine tomorrow to see if I can get different results on a different architecture, which should help rule out (or confirm 🙃) user error. I can also post my |
@g-2-s hmmm .. and the slider was at safer when you opened TB? hmmm there might be something else at play here - but this is weird since your FF test didn't exhibit this behavior @javulticat thanks - this is why we test :) what gets me is the result for all of them is identical for all six measurements, not even out by There are other prefs that the slider changes - see these - so any of those I only tested the baselinejit one (in FF) as a quick mimic of the slider in TB |
going to ping @PieroV for this AArch64 conundrum (IANAHardwareE) |
the iMac is my desktop - in About>system settings>general .. it says the chip is M1 - it's a year old and is one of these - https://www.apple.com/imac/specs/ (but not from the USA) - I got the lower end spec model in the shop (I had two options) - I only bought it so I could test stuff :) I'm not super savvy on hardware, but would be nice to know what causes these differences. I edit: the |
Have Standard and Safest as well:
DOCUMENT IFRAME
DOCUMENT IFRAME
DOCUMENT IFRAME
DOCUMENT IFRAME |
ok, that confirms what I thought. Sorry my test is a pain to copy the results and STR are a bit confusing original TB - #1789 (comment)
TB post above
i.e you opened at standard + tested, then set to safer + restarted + tested, then set to safest + restarted + tested so the original post must be another case of copy/paste gone wrong or human confusion? has to be since the new results are consistent with your FF results on the same machine the two safest tests when you allow JS to run will just return whatever state the browser was started in (for our test on recursion levels and stack lengths) thanks for testing :) have some 🍕 and 🍰 |
ok, I fubared my iMac result, I just retested - that
|
FF 121.0 on Debian Bookworm WORKER DOCUMENT IFRAME javascript.options.baselinejit = true |
Firefox 121.0, aarch64 Fedora Linux, M2 MacBook Air javascript.options.baselinejit = trueWORKER DOCUMENT IFRAME javascript.options.baselinejit = falseWORKER DOCUMENT IFRAME |
FF 121.0 Debian Bookworm javascript.options.baselinejit = false WORKER DOCUMENT IFRAME |
Sorry, I definitely don't have enough knowledge about this as well. But I wouldn't be too surprised if aarch64 was very different from the rest. TBB 13.0.8, Debian testing:
I can test on the same machine on Windows 10 bare metal and on other systems if you give me some more time, let me know 🙂 . Are you interested on VMs as well? If so I can test Windows 10/11 on a VM and also on Linux VMs. |
there's already a HW diff in audio - And here we have some aarch64 being different ( IANAE .. something about 64bit only ) - depending on our step a) results upstream, it may be we always load at disabled and that would solve that (if you know what I'm talking about) would be nice if someone like ted campbell (I think) from moz weighed in IDK if VMs are worth it just yet - they seem to mirror the host |
holy crap that's identical to my VM .. and you said you had different results :P
|
ok, got all I need - thanks everyone |
test: https://arkenfox.github.io/TZP/tests/recursion.html
example results: you can ignore iframe and worker
I'm determining if this (
level
) is stable enough as a fingerprint, and it seems so (we can round the number into buckets). So the next question becomes what does it return on different hardware. The other factor is enabling/disabling ion/jit etc - which AFAICT requires a restart for it to affect the results (I always close and re-test in a new tab)So here's some Tor Browser results to give you an idea
javascript.options.baselinejit
So what I'm interested in is on any device (os, vm), with any gecko browser (TB, FF) and any version - can you past me the results - just tell me those parameters - browser bitness, os, vm + underlying os, browser (TB, FF), version ... and tell me if you have opened
itthe browser withjavascript.options.baselinejit
= true or false. If you want, test both true and false (i.e change the value and restart)TIA
The text was updated successfully, but these errors were encountered: