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

seed failed in firefox #1134

Closed
Simplici opened this issue May 27, 2017 · 4 comments
Closed

seed failed in firefox #1134

Simplici opened this issue May 27, 2017 · 4 comments

Comments

@Simplici
Copy link

@Simplici Simplici commented May 27, 2017

seed not work on firefox, the onseed called back is not fired. the same code works fine on chrome.

there is nothing speical in the code:

    var seed = function(file, callback) {
        console.log('begin seed');
        _newClient().seed(file, function (torrent) {
            console.log('seed successful');
            callback(torrent.magnetURI);
        });
    };

navigator version: firefox 53.0.3 on Mac OS
webtorrent version: 0.98.18

@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented May 29, 2017

Do debug logs provide any information?

@Simplici

This comment has been minimized.

Copy link
Author

@Simplici Simplici commented May 30, 2017

no any error found in the console

@nativeB

This comment has been minimized.

Copy link

@nativeB nativeB commented Aug 12, 2017

Have this same problem it works fine in opera and chrome but not firefox
I used browserify to bundle the seeding demo code
Console only only reads caching disabled in ff51 due to bug;will be reenabled in ff52

After afew tries the console just reads typeerror asm. Js type error :disabled by debugger

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Apr 26, 2018

This issue appears stale since it has been open for a while with no activity. I'm going to close it for now. If this is still issue, please feel free to leave a comment or open a new issue.

@feross feross closed this Apr 26, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.