[Jack-Devel] JACK library on Windows causes crash if used within an ASLR application

[Jörg Müller]

> So if I understand correctly, JACK does not work with Windows 10 if ASLR 
> is enabled.
Slightly different. If you build an application that has ASLR enabled in
it's linker settings and use the JACK library, then your app will crash
on Windows 10 with JACK 1.9.11. Note, that linker setting is the default
since VS2012 and has become the norm for a lot of applications these
days. This also includes software trying to access the JACK ASIO driver,
so the crash extends to applications not using the JACK library at all
during compile-time.

> What is ASLR? Is this the Address Space Layout Randomization feature of 
> Windows? If so, Can it be disabled so that we can use JACK on Windows 10?
Yes, you can disable this at the system level. But since it is a
security feature, it is highly advised against doing this. Also, a
developer should not advise the end user to make such modifications.

> If we write our own application to connect to JACK, will that be a 
> problem too?
Currently, you can simply disable ASLR in the linker settings of your
software. The issue with the current situation - the JACK library
forcing a developer to disable this setting in it's own software - is
that you are not always in control of that. For instance, I'm developing
a JACK client that is used in a popular game engine (Unity). How that
game engine is built is beyond my control.

Apart from that, a library like JACK should not force you to disable
common security features.


Am 08.09.2019 um 17:11 schrieb Mechamania:
> Hi guys,
>
> So if I understand correctly, JACK does not work with Windows 10 if ASLR 
> is enabled.
>
> What is ASLR? Is this the Address Space Layout Randomization feature of 
> Windows? If so, Can it be disabled so that we can use JACK on Windows 10?
>
> If we write our own application to connect to JACK, will that be a 
> problem too?
>
>
> On 05/09/2019 15:45, Filipe Coelho wrote:
>> On 05.09.2019 14:18, Jörg Müller wrote:
>>> Is somebody of the JACK devs aware of that PR and looking into it?
>> I am aware of it, but am not doing any work on Windows related things 
>> at the moment.
>> Fixing the last details about metadata comes first, so 1.9.13 can be 
>> released.
>> And afterwards there is importing internal clients and latest things 
>> from jack1, so we can have feature parity.
>> Only after this (at least on my side) I will begin to take a look at 
>> win/macos issues.
>>
>> _______________________________________________
>> Jack-Devel mailing list
>> Jack-Devel at lists.jackaudio.org
>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
> _______________________________________________
> Jack-Devel mailing list
> Jack-Devel at lists.jackaudio.org
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org