Firefox v35 and v35.0.1 crashes when accessing the basketbuild site.
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)
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.
I did have to uninstall so I could access that site since many Android dev's are using it now. But here are a few quick attempts I did just a couple minutes ago after doing a clean install of v35.0.1 again.
https://crash-stats.mozilla.com/report/index/bp-9f0219fa-fedb-4ac6-aff1-09a162150207 https://crash-stats.mozilla.com/report/index/bp-1999a08b-fcd0-485d-935a-97fcc2150207 https://crash-stats.mozilla.com/report/index/bp-d22737a9-5fa8-4486-b5e2-f86c12150207 https://crash-stats.mozilla.com/report/index/bp-c6a9d7f7-93dc-429c-b9ad-dacbb2150207 https://crash-stats.mozilla.com/report/index/bp-30fe6d24-e4b9-447a-a2dc-7db0c2150207
this is happening with the peer5 downloader i suppose? (personally i apparently cannot reproduce it so far)
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.
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...