Jump to content
Sign in to follow this  
philipp.hofmann

MacOS: App-crash only if two displays are connected

Recommended Posts

Hi,

my app runs under Windows perfectly with two displays.
With MacOS and one display everything is fine also.
But my customer sometimes report the following error if they are using two displays:

Zugriffsverletzung bei Adresse 0000000102C2CD7D beim Zugriff auf Adresse 0000000000000000
At address: $0000000102C2CD7D (Fmx.Platform.Mac.TMacMetalView.displayLayer(Macapi.Quartzcore.CALayer) + 173)

Call stack:
icTrainer                 $0000000102633E4D SignalConverter + 45
icTrainer                 $0000000102633E20 SignalConverter + 0
icTrainer                 $000000010399F2DF DispatchToDelphi + 209
QuartzCore                $00007FF81E49363B -[CALayer display] + 184
QuartzCore                $00007FF81E492E9D CA::Layer::display_if_needed(CA::Transaction*) + 867
QuartzCore                $00007FF81E62BA24 CA::Context::commit_transaction(CA::Transaction*, double, double*) + 758
QuartzCore                $00007FF81E47401D CA::Transaction::commit() + 725
QuartzCore                $00007FF81E490CEE CA::Transaction::release_thread(void*) + 206
libsystem_pthread.dylib   $00007FF8159E526F _pthread_tsd_cleanup + 593
libsystem_pthread.dylib   $00007FF8159E787B _pthread_exit + 71
libsystem_pthread.dylib   $00007FF8159E4FDB pthread_exit + 42
icTrainer                 $000000010272F1A2 Classes.ThreadProc(Classes.TThread*) + 274
icTrainer                 $000000010261F587 ThreadWrapper(Pointer) + 55
libsystem_pthread.dylib   $00007FF8159E7202 _pthread_start + 99
libsystem_pthread.dylib   $00007FF8159E2BAB thread_start + 15

 

Is this a known problem?

Best regards, Philipp

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×