Opened 2 years ago

Closed 2 years ago

#19405 closed defect (user disappeared)

Error when accessing mega.nz

Reported by: torbacchi Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-6.0-issues
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When I try accessing mega.nz with Tor Browser 6.0.1, I get the following error message in a popup window:

An error occurred while loading MEGA.
Filename:
Exception: InternalError: allocation size overflow

The problem doesn't happen if I try with an older version of firefox (routed via Tor).

Child Tickets

Change History (7)

comment:1 Changed 2 years ago by gk

Status: newneeds_information

Does this happen with 6.0 as well (https://dist.torproject.org/torbrowser/6.0/)? On which platform? Is it enough loading mega.nz in my browser to see the problem or do I need to be logged in? Is the browser still working afterwards or does it crash?

comment:2 Changed 2 years ago by gk

Keywords: tbb-6.0-issues added
Resolution: duplicate
Status: needs_informationclosed

I think this is #19400. We have a user on the blog who confirms using a clean 6.0.1 fixes the problem for them.

comment:3 Changed 2 years ago by torbacchi

Resolution: duplicate
Status: closedreopened

I've just updated to 6.0.2 and the problem remains.

Then I tried the suggestion in https://trac.torproject.org/projects/tor/ticket/19400#comment:28 (remove the cached asmjs files which you can find under .../TorBrowser-Data/Browser/*.default/storage/temporary/) and the problem disappeared.

(Yes, I had alread visited mega.nz, so I had cached asmjs files)

I think you should include that cleanup suggestion in the release notes, because just updating to 6.0.2 won't fix the problem.

Last edited 2 years ago by torbacchi (previous) (diff)

comment:4 Changed 2 years ago by gk

Status: reopenedneeds_information

Could you test that again on your machine? Taking a clean 6.0.1, going to mega.nz and then updating to 6.0.2 and doing the same (see: https://dist.torproject.org/torbrowser/ for a 6.0.1)? The fix for #19417 should prevent your problems.

Are the cached asmjs files in 6.0.2 still there after you accessed mega.nz, closed Tor Browser and restarted it?

comment:5 Changed 2 years ago by gk

Oh, maybe that is due to you having disabled Private Browsing Mode in your Tor Browser? (clicking on the green onion -> Privacy and Security Settings... -> Don't record browsing history or website data (enables Private Browsing Mode) would show you the latter unchecked)

comment:6 Changed 2 years ago by bugzilla

user disappeared?

comment:7 Changed 2 years ago by gk

Resolution: user disappeared
Status: needs_informationclosed

Yeah, and "fixed" by disabling asmjs in 6.0.3 and the alphas anyway.

Note: See TracTickets for help on using tickets.