Same issue present on Windows machines. Older version prior to 15 works just fine.
For clarification, do you mean this error shows up in Whonix VMs running both on Windows and on non-Windows platforms? Or do you mean you’re seeing the same error when running Tor Browser directly on Windows itself? If you mean the latter, there’s probably not much we can do, since the issue isn’t OS-specific.
2 Likes
See wiki chapter Tor Browser Crash Errors.
1 Like
Yes, this error is present on Whonix running on Windows. This same issue also was found on Tor browser running directly on Windows too.
1 Like
Yes, tried on fresh install too. Could you please try and see if this is also reproducible on your end as well? I got Whonix on Windows and also Tor borwser directly on Windows and both got same issue.
Here’s the steps:
- Launch Tor browser using Profile Manager (-p argument or about:profiles).
- Delete all profiles and create a new profile.
- Start this profile with Profile Manager.
- Error appears as shown here.
1 Like
If Tor Browser running directly on Windows has the problem, you probably want to file a bug against Tor Browser itself. How to Report a Bug or Give Feedback - Get in touch - Support — Tor has a number of ways to reach out for support and report bugs.
1 Like
Surely but here at Whonix as a responsible team, we also need to first verify this issue to get more accurate info helping out more eventually.
1 Like
1 Like
related:
2 Likes
Turns out that the version 15.0 profile manager does not follow Firefox’s standard implementation for creating new profile names.
In Firefox a new profile is named “random string.user selected name” while in Tor’s new method is to only look for “profile.default” and anything other than that results in error. So if you create a new profile say, “poeirurt.hello123” and start to launch the browser, it fails.
Temporary solution is to delete the content of profile folder and allow the browser to recreate it while keeping “profile.default” structure as is.
1 Like