Closed Noctem closed 9 years ago
@9pigs can you test this?
@Noctem why can't we have a build that will work across all OS versions? (or if needed we can drop support for the most old one)
https://dl.dropboxusercontent.com/u/97502/qBittorrent-3.1.12-Yosemite.dmg downloaded, tested. crashed. Removed all via an uninstaller, repeated -- same result. Back to 3.1.3
Process: qbittorrent [1834] Path: /Applications/qbittorrent.app/Contents/MacOS/qbittorrent Identifier: org.qbittorrent Version: 3.1.12 (0) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: qbittorrent [1834] User ID: 501
Date/Time: 2015-02-04 09:25:49.090 -0800 OS Version: Mac OS X 10.10.2 (14C109) Report Version: 11 Anonymous UUID: 109314BE-C80A-BBC8-E0CA-B0B05FAAC8AB
Time Awake Since Boot: 4900 seconds
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000
Application Specific Information: /Applications/qbittorrent.app/Contents/MacOS/../Frameworks/libtorrent-rasterbar.7.dylib
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libtorrent-rasterbar.7.dylib 0x0000000103701f17 libtorrent::max_time() + 60223 1 dyld 0x00007fff6a211ceb ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 265 2 dyld 0x00007fff6a211e78 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40 3 dyld 0x00007fff6a20e871 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 305 4 dyld 0x00007fff6a20e806 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 198 5 dyld 0x00007fff6a20e6f8 ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 138 6 dyld 0x00007fff6a20e969 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 75 7 dyld 0x00007fff6a201245 dyld::initializeMainExecutable() + 187 8 dyld 0x00007fff6a204be1 dyld::_main(machoheader const, unsigned long, int, char const, char const, char const_, unsigned long) + 2716 9 dyld 0x00007fff6a200276 dyldbootstrap::start(machoheader const, int, char const__, long, machoheader const, unsigned long*) + 512 10 dyld 0x00007fff6a200036 _dyld_start + 54
Thread 0 crashed with X86 Thread State (64-bit): rax: 0x00000001037c03a0 rbx: 0x0000000103701eb0 rcx: 0x00007fff5cdbcc08 rdx: 0x00007fff5cdbcb68 rdi: 0x0000000000000001 rsi: 0x00007fff5cdbcb58 rbp: 0x00007fff5cdba270 rsp: 0x00007fff5cdba260 r8: 0x00007fff6a237660 r9: 0x00007fff749ce300 r10: 0x0000000000001c20 r11: 0x00007fff8a874f74 r12: 0x00000001037b3d70 r13: 0x00007fff6a237598 r14: 0x00007fff6a23eb00 r15: 0x00000000000000cc rip: 0x0000000103701f17 rfl: 0x0000000000010202 cr2: 0x0000000103701de0
Logical CPU: 1 Error Code: 0x00000000 Trap Number: 6
Binary Images:
0x102e43000 - 0x103474ff7 +org.qbittorrent (3.1.12 - 0)
External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 2656 thread_create: 0 thread_set_state: 0
VM Region Summary: ReadOnly portion of Libraries: Total=198.4M resident=147.5M(74%) swapped_out_or_unallocated=50.9M(26%) Writable regions: Total=25.4M written=1024K(4%) resident=1664K(6%) swapped_out=0K(0%) unallocated=23.8M(94%)
REGION TYPE VIRTUAL =========== ======= Kernel Alloc Once 4K MALLOC 16.4M MALLOC (admin) 32K STACK GUARD 56.0M Stack 8192K VM_ALLOCATE 8K DATA 14.3M IMAGE 528K LINKEDIT 73.4M TEXT 125.0M __UNICODE 544K shared memory 4K =========== ======= TOTAL 294.2M
@sledgehammer999 I'm trying to figure that out. I compiled qBittorrent and all of its dependencies on OS X 10.10 with -mmacosx-version-min=10.7
for that Mavericks / Mountain Lion binary, but it crashed on my 10.7 machine.
The Any binary should work on everything (at least after 10.7), It works on my 10.10 system. But ideally we'd distribute something using a newer compiler/SDK if possible.
@9Pigs Thanks for trying that. Did you test either of the other two binaries? Theoretically they should all work on Yosemite, they do on the Yosemite system that compiled them anyways.
Trying the other 2 via uninstall/ fresh start: https://dl.dropboxusercontent.com/u/97502/qBittorrent-3.1.12-Other.dmg crashed
Process: qbittorrent [2271] Path: /Applications/qbittorrent.app/Contents/MacOS/qbittorrent Identifier: org.qbittorrent Version: 3.1.12 (???) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: qbittorrent [2271] User ID: 501
Date/Time: 2015-02-04 11:02:43.221 -0800 OS Version: Mac OS X 10.10.2 (14C109) Report Version: 11 Anonymous UUID: 109314BE-C80A-BBC8-E0CA-B0B05FAAC8AB
Time Awake Since Boot: 10000 seconds
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000
Application Specific Information: /Applications/qbittorrent.app/Contents/MacOS/../Frameworks/libtorrent-rasterbar.7.dylib
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libtorrent-rasterbar.7.dylib 0x000000010a7248bf libtorrent::max_time() + 67290 1 dyld 0x00007fff63627ceb ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 265 2 dyld 0x00007fff63627e78 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40 3 dyld 0x00007fff63624871 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 305 4 dyld 0x00007fff63624806 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 198 5 dyld 0x00007fff636246f8 ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 138 6 dyld 0x00007fff63624969 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 75 7 dyld 0x00007fff63617245 dyld::initializeMainExecutable() + 187 8 dyld 0x00007fff6361abe1 dyld::_main(machoheader const, unsigned long, int, char const, char const, char const_, unsigned long) + 2716 9 dyld 0x00007fff63616276 dyldbootstrap::start(machoheader const, int, char const__, long, machoheader const, unsigned long*) + 512 10 dyld 0x00007fff63616036 _dyld_start + 54
Thread 0 crashed with X86 Thread State (64-bit): rax: 0x000000010a8362c0 rbx: 0x000000010a835ea0 rcx: 0x0000000000000000 rdx: 0x00007fff76bbe0d0 rdi: 0x00002b0000002c03 rsi: 0x00002c0000002c00 rbp: 0x00007fff55dc6220 rsp: 0x00007fff55dc6210 r8: 0x00007fff55dc6180 r9: 0x0000000000000005 r10: 0x00000000dfce22b3 r11: 0x00000000dfcef464 r12: 0x000000010a829d20 r13: 0x00007fff6364d598 r14: 0x000000010a56a000 r15: 0x00000000000000cc rip: 0x000000010a7248bf rfl: 0x0000000000010202 cr2: 0x000000010a724760
Logical CPU: 1 Error Code: 0x00000000 Trap Number: 6
Binary Images:
0x109e37000 - 0x10a490ff7 +org.qbittorrent (3.1.12 - ???)
External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 4653 thread_create: 0 thread_set_state: 0
VM Region Summary: ReadOnly portion of Libraries: Total=199.7M resident=152.9M(77%) swapped_out_or_unallocated=46.8M(23%) Writable regions: Total=18.3M written=932K(5%) resident=1892K(10%) swapped_out=0K(0%) unallocated=16.5M(90%)
REGION TYPE VIRTUAL =========== ======= Kernel Alloc Once 4K MALLOC 9572K MALLOC (admin) 32K STACK GUARD 56.0M Stack 8192K VM_ALLOCATE 8K DATA 14.4M IMAGE 528K LINKEDIT 73.4M TEXT 126.3M __UNICODE 544K shared memory 4K =========== ======= TOTAL 288.5M
Smoke test of https://dl.dropboxusercontent.com/u/97502/qBittorrent-3.1.12-Lion.dmg resulted in this crash:
Process: qbittorrent [2382] Path: /Applications/qbittorrent.app/Contents/MacOS/qbittorrent Identifier: org.qbittorrent Version: ??? Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: qbittorrent [2382] User ID: 501
Date/Time: 2015-02-04 11:09:24.441 -0800 OS Version: Mac OS X 10.10.2 (14C109) Report Version: 11 Anonymous UUID: 109314BE-C80A-BBC8-E0CA-B0B05FAAC8AB
Time Awake Since Boot: 11000 seconds
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information: dyld: launch, loading dependent libraries
Dyld Error Message: Library not loaded: @@HOMEBREW_PREFIX@@/lib/libboost_system-mt.dylib Referenced from: /Applications/qbittorrent.app/Contents/MacOS/qbittorrent Reason: image not found
Binary Images:
0x7fff6998d000 - 0x7fff699c3837 dyld (353.2.1) <65DCCB06-339C-3E25-9702-600A28291D0E> /usr/lib/dyld
0x7fff8a73d000 - 0x7fff8a7afff7 com.apple.framework.IOKit (2.0.2 - 1050.10.8)
Oh, a library reference on that last one is definitely messed up. I think I uploaded the wrong bundle, I'll replace it later.
@9Pigs Could you try my new alternate-beta?
@Noctem That loooong link gave me a 404. I kept chopping off the tail til I got to https://github.com/Noctem/qBittorrent/releases/ and snagged the 3.1.2 alternate beta. It launched a minute ago without a crash. I'll let her run as I sleep and get back to you
Just fixed the link.
Great, thanks for doing this. If you're feeling adventurous you could try the normal beta too, but I would expect that to crash on systems that crashed with the previous binaries I uploaded.
I sorry I am late to the game.
The ImageLoaderMachO::doModInitFunctions()
is similar with the one that they got from @Bipsen 's builds.
If @9pigs still reports the same crash with the new beta, I would ask you to build libtorrent with "build-bottle" if you can. It is my understand that this makes homebrew build the code with switches tha make it work across all supported MAC hardware.
@sledgehammer999 Oh wow, I totally forgot about that feature. Thanks, that seems to have fixed it.
@9Pigs Could you try this new beta2? It works on my i5 Yosemite and Core 2 Lion machines, so if I can get confirmation from someone else we should be able to get rid of the "alternate-beta".
@mmleif @ragmaxone can you try this new beta2 build and confirm that it works on your machine?
Some correction: I wanted to say @DomT4's builds not @Bipsen's
@sledgehammer999 @Noctem Got it. Woke up to alternate beta looking OK -- with that "needs to be restarted" thing showing. Downloading your beta2 right now. :)
Update: Started up OK and resumed normally. did a quick check of prefs, search engine, etc
Beta 2 working perfect here! I'm on MacBook Pro with Intel Core 2 Duo using Yosemite 10.10.2. Thanks so much.
So we're ready to proceed to an official v3.1.12 release. @Noctem will you be around to provide a build for that just like you did with beta2?
@qbittorrent/qbittorrent-frequent-contributors @ngosang (read below) Since I am going to release another version in the v3.1.x series, I want you to tell if there is any critical commit from master that I need to backport to the v3_1_x branch. -Take a look at the branch mentioned in the first post first-. I am going to include also commits 5d79fcd and 24a1c9b1 Is something else that I am forgetting?
None of my contributions is critical. There is a date for v3.2?
There is a date for v3.2?
No ETA. But a rough milestone target: https://github.com/qbittorrent/qBittorrent/milestones/v3.2.0
No ETA. But a rough milestone target.
I saw the milestone and looks too ambitious. The 3.2 release could be delayed months, even years. Anyway, I use the development version so I don't have to wait for it. :smile:
The 3.2 release could be delayed months, even years.
This is what I was thinking the past few days. There are some 5-6 easily implementable issues by me. I am just waiting my new rig that will allow me to have linux VMs instead of constantly rebooting between OS's. (and allow faster compilations). I should have either the weekend or the coming week. But since there is constant WebUI work being done, I have no problem delaying more. The biggest issue is finally going and choosing a new icon set for the Windows version, since I have promised that in the forum for v3.2.0.
I don't want to tell you how to do your job. But if you want to speed things up a bit I give you some advices. The most important thing is to set an approximate date for the release, for example 1 or 2 months. Tell major developers that for that date the big changes they are making must be completed and merged. If they don't have enough time to finish, they should divide the work so that it is possible to have a portion running on time. There are some changes, as the code style or the build system, that are not important for users and may be delayed.
@Noctem will you be around to provide a build for that just like you did with beta2?
Yeah, I'll be around. And now that I have a working build environment set up I should be able to produce new bundles quickly. beta2 doesn't actually contain anything indicating that it's pre-release aside from the filename of the DMG, the version string of the application is just 3.1.12, so if you want to release that as-is it should be ready to go after the DMG is renamed. But if you're bringing more changes to that release, I'm ready and willing to build the new one.
If the changes to support libtorrent-rasterbar 1.0.x and boost 1.57.0 can easily be integrated and you're comfortable with their stability (they're both working smoothly so far as I can tell in my daily use of the master branch), I would be interested in bundling those as soon as possible. I'm a tad obsessive about keeping things up-to-date, but I'll understand if you think those commits are overly dependent on other moving parts or otherwise not ready for release.
DMG, the version string of the application is just 3.1.12,
You shouldn't have done a version bump in the first place...
libtorrent 1.0.x cannot be backported. It is too much work. boost 1.57 works as is on Windows(and linux I think). Tomorrow I'll push the changes into the official v3_1_x branch, version bump and tag. Then I'll leave a note here for you to get notified too.
PS: For the time being, take down the versions mentioned at your first post so we don't have users running 2 releases of v3.1.12.
Alright, sorry about that. I uploaded a new bundle with 3.1.11 as the version string for anyone else that wants to do testing before the release.
_v3_1x-mac still faces the problem described in #2119.
moc -DBOOST_ASIO_DYN_LINK -DWITH_GEOIP_EMBEDDED -DQT_NO_DEBUG_OUTPUT -DVERSION=\"v3.1.11\" -DVERSION_MAJOR=3 -DVERSION_MINOR=1 -DVERSION_BUGFIX=11 -DQT_NO_CAST_TO_ASCII -DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS -DBOOST_FILESYSTEM_VERSION=2 -DTORRENT_USE_OPENSSL -DBOOST_ASIO_HASH_MAP_BUCKETS=1021 -DBOOST_EXCEPTION_DISABLE -DBOOST_ASIO_ENABLE_CANCELIO -DTORRENT_LINKING_SHARED -DQT_NO_DEBUG -DQT_XML_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I../../homebrew/Cellar/qt/4.8.6/mkspecs/unsupported/macx-clang-libc++ -I. -I../../homebrew/Cellar/qt/4.8.6/lib/QtCore.framework/Versions/4/Headers -I../../homebrew/Cellar/qt/4.8.6/lib/QtCore.framework/Versions/4/Headers -I../../homebrew/Cellar/qt/4.8.6/lib/QtNetwork.framework/Versions/4/Headers -I../../homebrew/Cellar/qt/4.8.6/lib/QtNetwork.framework/Versions/4/Headers -I../../homebrew/Cellar/qt/4.8.6/lib/QtGui.framework/Versions/4/Headers -I../../homebrew/Cellar/qt/4.8.6/lib/QtGui.framework/Versions/4/Headers -I../../homebrew/Cellar/qt/4.8.6/lib/QtXml.framework/Versions/4/Headers -I../../homebrew/Cellar/qt/4.8.6/lib/QtXml.framework/Versions/4/Headers -I../../homebrew/Cellar/qt/4.8.6/include -I/usr/local/include -I/opt/local/include -I/usr/include -I. -Iqtsingleapp -Iqtlibtorrent -Iwebui -Iwebui/qjson -Itracker -Ipreferences -Ilineedit/src -Iproperties -Isearchengine -Irss -Itorrentcreator -Igeoip -Ipowermanagement -I../../homebrew/Cellar/libtorrent-rasterbar/0.16.19/include -I../../homebrew/Cellar/libtorrent-rasterbar/0.16.19/include/libtorrent -I. -I. -F../../homebrew/Cellar/qt/4.8.6/lib -D__APPLE__ -D__GNUC__ main.cpp -o main.moc
usr/local/Cellar/boost/1.57.0/include/boost/type_traits/detail/has_binary_operator.hp:50: Parse error at "BOOST_JOIN"
Makefile:1589: recipe for target 'main.moc' failed
make[1]: *** [main.moc] Error 1
Sorry for missing your email, @sledgehammer999
I will try it tonight in my end as well.
On 13 February 2015 at 00:55, sledgehammer999 notifications@github.com wrote:
@mmleif https://github.com/mmleif @ragmaxone https://github.com/ragmaxone can you try this new beta2 build and confirm that it works on your machine?
— Reply to this email directly or view it on GitHub https://github.com/qbittorrent/qBittorrent/issues/2497#issuecomment-74073691 .
Best regards, Ken
@Noctem it seems to much work for backporting the fix for 1.57.
Can I have the link of the latest beta (beta2?) ?
Thanks.
I am going to include also commits 5d79fcd and 24a1c9b
You retarget search engines URL to src/gui/searchengines. But we have some request to add access to search engines from webui so we may need to move the base part of it (all excluding gui code) in the core.
so we may need to move the base part of it (all excluding gui code) in the core.
Or it may be better to move engines itself (without c++ code) to dist folder?
Can I have the link of the latest beta (beta2?) ?
@mmleif I took it down, but the test build is the same thing, just with a different version string.
@Noctem I just downloaded your version-corrected one. Heads up that the first launch gave me this (I chose "no" this time)
@glassez even though I am skeptical about exposing searches in the webui(isn't it a bit redundant) I am not totally against it. Nevertheless, if you don't have any objections I'll move searchengines back to their original position.
@9Pigs I suppose the new beta is marked as v3.1.11. That's why it sees the "newer" v3.1.11.1. It will be fixed with the official release which will be v3.1.12 thus newer.
@Noctem a little more patience. Today I have my new pc parts and I'll rebuild my rig. Afterwards I'll come and make the necessary steps for releasing.
Nevertheless, if you don't have any objections I'll move searchengines back to their original position.
If you will return back only the plugins (I mean .py files, icons etc.), it will be a real compromise. And appropriate .qrc file can be placed in the src, by analogy with the images.
Good news!
I downloaded the test build, drag it in the application folder and replaced the existing qBittorent, it is working now !
The downloaded the file says 3.1.12 but after install it says 3.1.11 still.
On 14 Feb 2015, at 5:50 am, David Christenson notifications@github.com wrote:
@mmleif https://github.com/mmleif I took it down, but the test build https://github.com/Noctem/qBittorrent/releases/download/3.1.x-test/qBittorrent-3.1.11-testbuild.dmg is the same thing, just with a different version string.
— Reply to this email directly or view it on GitHub https://github.com/qbittorrent/qBittorrent/issues/2497#issuecomment-74305191.
I downloaded the test build, drag it in the application folder and replaced the existing qBittorent, it is working now !
Glad to hear it, @mmleif.
The downloaded the file says 3.1.12 but after install it says 3.1.11 still.
Yeah, I forgot to change the title of the DMG.
a little more patience. Today I have my new pc parts and I'll rebuild my rig. Afterwards I'll come and make the necessary steps for releasing.
@sledgehammer999 Sounds good, no rush. Congrats on the new parts, that's always fun.
Thanks for all the hard work!
On 15 Feb 2015, at 2:19 am, David Christenson notifications@github.com wrote:
I downloaded the test build, drag it in the application folder and replaced the existing qBittorent, it is working now !
Glad to hear it, @mmleif.
The downloaded the file says 3.1.12 but after install it says 3.1.11 still.
Yeah, I forgot to change the title of the DMG.
a little more patience. Today I have my new pc parts and I'll rebuild my rig. Afterwards I'll come and make the necessary steps for releasing.
@sledgehammer999 Sounds good, no rush. Congrats on the new parts, that's always fun.
— Reply to this email directly or view it on GitHub.
working here too. thanks!!
If you will return back only the plugins (I mean .py files, icons etc.), it will be a real compromise. And appropriate .qrc file can be placed in the src, by analogy with the images.
@glassez What is the meaning of "compromise" in this senctence? Negative/positive/neutral? about the qrc: it also contains the .py files so we can't move it there.
A compromise between those that plug-ins were at the old place (for compatibility), and c++ code was in the place where the structure of the application instructs it to be (#2433).
@sledgehammer999 What's your status on this?
@Noctem sometime between now and ~2 hours later I'll push the final commits for v3.1.12
@Noctem I have released v3.1.12. When you have the dmg ready tag me here so I can upload it to the official repos.
@sledgehammer999 Here you go.
SHA-1: 37c01ec068c8d4cc289bef44f84618640c6904f8
SHA-256: bc98faea71586f7a15a011429cece439756ae27898771c7ea04511fe5362072a
@sledgehammer999 @Noctem Launched fine --- looks good in picking up where the 3.3.11 test left off. I'll do some further smoke testing and report back if I see problem.
Thanks to both of you for your working this thing out!
@Noctem thank you for your patience and your build. When a new release will happen, build it and inform me via email (sledgehammer999 at qbittorrent dot org). @9Pigs thanks for your patience too and your testing.
@sledgehammer999 You're welcome. I noticed you have a 3.2.0alpha build available for Windows on FossHub, do you want me to create one for OS X?
do you want me to create one for OS X?
Sure. Follow the same naming scheme I do for the Windows alpha. PS: use qt4 not qt5. Also use libtorrent 1.0.x.
@Noctem some users (by email and forum) report that the v3.1.12 package presents the UI lock and asks for a password. Supposedly they didn't enable that setting before. We have instructions here on how to delete the UI lock: https://github.com/qbittorrent/qBittorrent/wiki/I-forgot-my-UI-lock-password They tried it and they can't get it to work. Can you confirm that the instructions are correct and that they actually work?
I have a couple binaries for people to test. They were compiled from this branch.
OS X Test Build In this build, qBittorrent and its dependencies were built on OS X 10.10 using libc++. SHA1:
898342e4556a8bf4189667c8bd0cac68ff570623
They are both built with Qt 4.8.6, Boost 1.56.0, libtorrent-rasterbar 0.16.19, and OpenSSL 1.0.2.