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
[Windows 7, 8 & 8.1] 0.15.1 crashes upon video playback (very beginning, reproducable) #1886
Comments
Hey there, before we test this further, could you please run this test and return back with the results? Please try this build and attempt to watch a video. Let me know if it crashed. Then please try this build and do the same thing. My guess is that it might have something to do with the new Electron release and Windows 7. If the first build works and the second one does not then that very well seems to be the case. If both of these builds return the same result then we'll have to dig further. |
Just did a search and found this issue posted a couple of days ago. Looks like it's an Electron issue. We'll have to wait for this to be fixed by the devs upstream. |
It seems to be like you suspected: Freetube installed from
p.S.: So that means: wait for 0.15.2 for Win7 users? |
Unfortunately yes. I'm not keen on downgrading Electron again as the latest release has fixed a variety of issues even if it introduced this one. The Electron devs are aware of the issue though so hopefully a fix will be out soon. For now, my only suggestions are to either downgrade FreeTube (Either to v0.15.0 or to the nightly build I linked) or to change your OS (Regardless if that's to Windows 10, Linux, etc). We try to stay as close to the latest release of Electron as possible so we'll push out a fix as soon as we can. Keeping an eye on that issue I linked will give you a better idea of when it'll be fixed. Sorry I don't have better news for you. |
I understand; Thank you for the explanation and FreeTube in general. |
Win7 also here. |
Win7 crashes on Playback with Build freetube-0.15.1-nightly-1334-win-x64-portable |
Hello: Add my system to the list. Version 15.0 did not crash. Some of the issues addressed by the v 15.1 update were present on v15.0, buffering issues mostly. I can open the app (15.1) on my PC. All menus and search appear to work. As soon as I click on a video link, the video image (still image) will open and the audio plays for about 3 seconds. Then I get a windows crash message as pasted below. The video never begins. Please don't ask me to (down)grade to Win 10. When I can't continue to use Win7,its Linux for me. I wont get into it here for this problem report. All updates to Jan 2020 are on the Win7 x64 SP1 system. Please contact me if you need more information. The system is running a core i7 6700 with 8 Gb ram. Locally stored videos play fine on vlc. Problem signature: The system is running a core i7 6700 with 8 Gb ram. |
I'm having the same problem on |
Windows 8.1 crashes as well. |
Windows 8.1 as well, same crashes. I can also confirm the 1322 nightly build works fine. |
Windows 7 guy here, first link works but the second one crashes at one second of playback |
I am in a similar but not identical situation. I'm also running Windows 7. I cannot run the latest version of FreeTube and the build that works for @Leza89 did not work for me. Instead, freetube-0.15.0-nightly-1322-win-x64-portable seems to be working for me. |
Please let us know the moment any build that fixes this problem is released. There are other problems with 0.15.1 that I've held off reporting in the hope that the next version obsoletes them. |
This will be addressed soon in our upcoming release. |
Behavior of the program
Expected behavior
Video playback without Freetube crashing and being unresponsive.
To Reproduce
Please add all steps to reproduce the behavior:
Screenshots/DevConLogs
DevTools failed to load source map: Could not parse content for file:///C:/Program%20Files/FreeTube/resources/app.asar/dist/index.js.map: Unexpected end of JSON input
Environment Information (please complete the following information):
The text was updated successfully, but these errors were encountered: