| Ticket UUID: | daf63ec2bee4bc2767aa26a0101461b7e7cdfcbf | |||
| Title: | Ripcord crashes silently on a Celeron processor | |||
| Status: | Fixed | Type: | Bug | |
| Severity: | Important | Priority: | Low | |
| Subsystem: | Windows | Resolution: | Fixed | |
| Last Modified: | 2020-07-26 05:10:33 | |||
| Version Found In: | 0.3.4 | |||
diya — 2018-10-03 14:39:14Ripcord crashes immediately upon starting it up. It just opened, then freezes for 4 seconds, then closes itself with no error messages or crash dialog. A mod told me that this is the OpenSSL's fault in the code that is trying to use a command that's not present in a Celeron CPU. | ||||
|
tmad40blue — 2018-10-03 14:49:13 A few more details: That mod was me, and the issue is that OpenSSL didn't previously have support (or it was broken) for Intel SHA extensions on Goldmont CPUs. Relevant GitHub issue: https://github.com/openssl/openssl/issues/3241 diya and I were able to create a workaround by creating a launch.bat file with the following contents: set OPENSSL_ia32cap=:0
start ripcord | ||||
|
cancel — 2020-01-13 21:09:12 Reported to also affect Intel Core i5 1035G4 CPU, which is in the Microsoft Surface 7. | ||||
|
cancel — 2020-01-16 23:44:47 Also reported to affect Intel(R) Celeron(R) CPU N3350 | ||||
|
cancel — 2020-04-11 15:48:44 Also reported to affect Intel® Core™ i7-1065G7 ("Products formerly Ice Lake") | ||||
|
cancel — 2020-07-04 15:11:10 This is fixed in the next update. I've compiled new OpenSSL binaries, and they will be bundled with the next release on Windows. In the meantime, here's a zip of version 0.4.26, but with the OpenSSL binaries updated to the new version: If you use this test pre-release of Ripcord, the .bat launch workaround is not needed on the listed CPUs (and whatever other ones the old OpenSSL may crash on.) | ||||
|
cancel — 2020-07-26 05:10:33 Test version updated, take a look at the directory contents here for the newest build: https://cancel.fm/dl/test/ | ||||