adl quit unexpectedly about adobe-runtime-support HOT 8 OPEN

The same issue: #3166

from adobe-runtime-support.

Same issue.
'application descriptor file not specified
usage:
adl ( -runtime )? ( -pubid )? -nodebug? ( -profile PROFILE )? ( -extdir )? ( -screensize SCREEN_SIZE )? ? ( -- ... )?
adl -help

PROFILE : mobileDevice|extendedMobileDevice|desktop|extendedDesktop|tv|extendedTV
SCREEN_SIZE : ( x:x )|PREDEFINED_SCREEN_SIZE
PREDEFINED_SCREEN_SIZE : iPhone|iPhoneRetina|iPhone5Retina|iPhone6|iPhone6Plus|iPod|iPodRetina|iPod5Retina|iPad|iPadRetina|Droid|NexusOne|SamsungGalaxyS|SamsungGalaxyTab|QVGA|WQVGA|FWQVGA|HVGA|WVGA|FWVGA|1080|720|480

Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]
'

from adobe-runtime-support.

same problem on AIR SDK 50.2.5.1 on macOS, adl crash at start up.
works fine on AIR SDK 50.2.4.5, AIR SDK 51.0.0.4

from adobe-runtime-support.

Hi, @pol2095 tried to do the xattr command twice. No chance. Crashes. What a mess. Using Sonoma 14.4.1

from adobe-runtime-support.

Same problem, adt work correctly, Harman changed something which crashes adl...

from adobe-runtime-support.

Yes :-( for some reason there's a crash happening within socket connections relating to the debugger. We can't actually reproduce this here, I have no idea why it's happening on some machines and not others, but with a bit of help in remote debugging from @itlancer we have got a patch available:
https://transfer.harman.com/link/7pdk2vBMTnMMFQbL3ehVOS

This contains the "Adobe AIR.framework" folder that needs to be copied over the top of the one in
/runtimes/air/mac

thanks

from adobe-runtime-support.

Hi @ajwfrost, it is now the same with 50.2.4.5
Attached the report file.
But with the patch it is working now.
crash.txt

from adobe-runtime-support.

That looks like the same issue; curious that it's appearing in 50.2.4.5, although looking at it, we had a couple of reports there of a 'hang' on start-up on iOS which is all related.. essentially a side-effect of trying to ensure we keep the behaviour the same for old applications having implemented the new TCP 'nagle' feature..

from adobe-runtime-support.