Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox v35 and v35.0.1 crashes when accessing the basketbuild site.

  • 5 replies
  • 1 has this problem
  • 3 views
  • Last reply by philipp

more options

This does not occur in any of the previous builds of Firefox.

The first attempt or two at downloading from Basketbuild works after a clean install. But then after that it causes Firefox to crash. I have submitted a crash report each time.

An example to try a couple times to see if it happens to you: https://s.basketbuild.com/devs/TKruzze/Android%205.0.1%20GApps/Pico-Modular%20GApps

This does not occur in any of the previous builds of Firefox. The first attempt or two at downloading from Basketbuild works after a clean install. But then after that it causes Firefox to crash. I have submitted a crash report each time. An example to try a couple times to see if it happens to you: https://s.basketbuild.com/devs/TKruzze/Android%205.0.1%20GApps/Pico-Modular%20GApps

All Replies (5)

more options

hello, could you provide your latest few submitted crash reports? please enter about:crashes into the location bar, copy the latest few report ids from there starting with bp- & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes.

more options
more options

this is happening with the peer5 downloader i suppose? (personally i apparently cannot reproduce it so far)

more options

Yes, for me after the initial download starts (which uses the peer5 downloader by default), regardless if I choose not to use the peer5 downloader after that it still causes FF to crash once the page loads. If it matters all of the pc's are running 64bit Windows 8.1. I say all, because this is reproducible, at least for me, on 12 Windows 8.1 devices.

It also doesn't occur with any version below v35.

more options

thanks, i've cross-referenced your information at the appropriate bug report here. hopefully that will help mozilla's developers. you might want to follow along this bug for progress as well...