FMP 12 Crashing during window intensive operations on OS X 10.9.2

Discussion:

Michael MacKinnon

2014-03-25 19:31:23 UTC

FMP 12 repeatedly crashes during 'window intensive' operations on OS X, basically where there are scripts with lots of 'New Window' and 'Close Window' script steps (when these are used in a loop for instance).

Errors in console:

2014-03-24 09:51:16.444 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.444 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.445 FileMaker Pro[18667]: CoreAnimation: failed to allocate 11041024 bytes
2014-03-24 09:51:16.447 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.447 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.580 FileMaker Pro[18667]: CoreAnimation: failed to allocate 11041024 bytes

2014-03-24 09:51:16.923 FileMaker Pro[18667]: FileMaker Pro(18667,0xa17c71a8) malloc: *** mach_vm_map(size=11042816) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

2014-03-24 09:51:17.433 FileMaker Pro[18667]: CGSImageDataLock: Cannot allocate memory

Then finally FileMaker Pro 12 will crash

Process: FileMaker Pro [18667]
Path: /Applications/FileMaker Pro 12 Advanced/FileMaker Pro Advanced.app/Contents/MacOS/FileMaker Pro
Identifier: com.filemaker.client.advanced12
Version: 12.0.5 (12.0.5)
Code Type: X86 (Native)
Parent Process: launchd [154]
Responsible: FileMaker Pro [18667]
User ID: 501

Date/Time: 2014-03-24 09:51:22.144 -0600
OS Version: Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: B8CEBD31-8387-ADD1-43BC-0723473B05E9

Sleep/Wake UUID: 381143E4-3E75-48A3-A73B-792E98AC0FE8

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information:
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
abort() called

------

NOTES

Happens only when working remotely (using FileMaker 12 Server Advanced), does not crash when I'm using a copy of the database on the local computer

Doesn't occur at all on Windows 7 / FileMaker Pro Advanced 12.0v4

FIXES

My only solution is to re-write the scripts to not use the 'New Window' and 'Close Window' steps so much. But any other advice would be appreciated.

From reading the Console it seems to be some type of error with memory allocation, but I don't fully understand the messages.

Cheers,

Mike

Samuel Herschbein

2014-03-25 20:40:53 UTC

Permalink

Mike->

I don't have a definitive answer, but some conjectures and long-shot suggestions.

OS X has had major window focus issues since Snow Leopard, windows don't get focus when they should and vice-versa. Most commonly people have windows where you can't click or control them. The only way to get them to respond is to minimize them from the Window menu and then select them from the Window menu.

My conjecture is the _CGSLockWindow errors are related to the window focus: OS X is trying to work with the wrong window (or no window...). This could be causing the CoreAnimation memory allocation fails.

What I would try: open the windows off-screen so the window manager doesn't have to try and display them. It may also help to put a short delay after creating a window to give the OS time to settle down.

Sam

Post by Michael MacKinnon
FMP 12 repeatedly crashes during 'window intensive' operations on OS X, basically where there are scripts with lots of 'New Window' and 'Close Window' script steps (when these are used in a loop for instance).
2014-03-24 09:51:16.444 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.444 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.445 FileMaker Pro[18667]: CoreAnimation: failed to allocate 11041024 bytes
2014-03-24 09:51:16.447 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.447 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.580 FileMaker Pro[18667]: CoreAnimation: failed to allocate 11041024 bytes
2014-03-24 09:51:16.923 FileMaker Pro[18667]: FileMaker Pro(18667,0xa17c71a8) malloc: *** mach_vm_map(size=11042816) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
2014-03-24 09:51:17.433 FileMaker Pro[18667]: CGSImageDataLock: Cannot allocate memory
Then finally FileMaker Pro 12 will crash
Process: FileMaker Pro [18667]
Path: /Applications/FileMaker Pro 12 Advanced/FileMaker Pro Advanced.app/Contents/MacOS/FileMaker Pro
Identifier: com.filemaker.client.advanced12
Version: 12.0.5 (12.0.5)
Code Type: X86 (Native)
Parent Process: launchd [154]
Responsible: FileMaker Pro [18667]
User ID: 501
Date/Time: 2014-03-24 09:51:22.144 -0600
OS Version: Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: B8CEBD31-8387-ADD1-43BC-0723473B05E9
Sleep/Wake UUID: 381143E4-3E75-48A3-A73B-792E98AC0FE8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
abort() called
------
NOTES
Happens only when working remotely (using FileMaker 12 Server Advanced), does not crash when I'm using a copy of the database on the local computer
Doesn't occur at all on Windows 7 / FileMaker Pro Advanced 12.0v4
FIXES
My only solution is to re-write the scripts to not use the 'New Window' and 'Close Window' steps so much. But any other advice would be appreciated.
From reading the Console it seems to be some type of error with memory allocation, but I don't fully understand the messages.
Cheers,
Mike
_______________________________________________
FMPexperts mailing list
http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au

Michael MacKinnon

2014-03-25 20:50:17 UTC

Permalink

Thanks for the feedback Sam!

Since this only happens over the Internet/WAN I think what you're saying is right. It could be that the content inside the windows are perhaps not rendering fast enough which is causing issues. A small delay should solve this (since the issue doesn't show up on the local machine or even over a LAN).

With Windows I can open the windows off screen but with OS X it always seems to draw them at 0,0 (doesn't accept negative values) so they remain visible.

Cheers,

Mike

On Mar 25, 2014, at 02:40 PM, Samuel Herschbein <sam-***@public.gmane.org> wrote:

Mike- >

I don't have a definitive answer, but some conjectures and long-shot suggestions.

OS X has had major window focus issues since Snow Leopard, windows don't get focus when they should and vice-versa. Most commonly people have windows where you can't click or control them. The only way to get them to respond is to minimize them from the Window menu and then select them from the Window menu.

My conjecture is the _CGSLockWindow errors are related to the window focus: OS X is trying to work with the wrong window (or no window...). This could be causing the CoreAnimation memory allocation fails.

What I would try: open the windows off-screen so the window manager doesn't have to try and display them. It may also help to put a short delay after creating a window to give the OS time to settle down.

Sam

On Mar 25, 2014, at 12:31 PM, Michael MacKinnon <michaelmackinnon-***@public.gmane.org > wrote:

> FMP 12 repeatedly crashes during 'window intensive' operations on OS X, basically where there are scripts with lots of 'New Window' and 'Close Window' script steps (when these are used in a loop for instance).
>
> Errors in console:
>
> 2014-03-24 09:51:16.444 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
> 2014-03-24 09:51:16.444 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
> 2014-03-24 09:51:16.445 FileMaker Pro[18667]: CoreAnimation: failed to allocate 11041024 bytes
> 2014-03-24 09:51:16.447 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
> 2014-03-24 09:51:16.447 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
> 2014-03-24 09:51:16.580 FileMaker Pro[18667]: CoreAnimation: failed to allocate 11041024 bytes
>
> 2014-03-24 09:51:16.923 FileMaker Pro[18667]: FileMaker Pro(18667,0xa17c71a8) malloc: *** mach_vm_map(size=11042816) failed (error code=3)
> *** error: can't allocate region
> *** set a breakpoint in malloc_error_break to debug
>
> 2014-03-24 09:51:17.433 FileMaker Pro[18667]: CGSImageDataLock: Cannot allocate memory
>
>
>
> Then finally FileMaker Pro 12 will crash
>
> Process: FileMaker Pro [18667]
> Path: /Applications/FileMaker Pro 12 Advanced/FileMaker Pro Advanced.app/Contents/MacOS/FileMaker Pro
> Identifier: com.filemaker.client.advanced12
> Version: 12.0.5 (12.0.5)
> Code Type: X86 (Native)
> Parent Process: launchd [154]
> Responsible: FileMaker Pro [18667]
> User ID: 501
>
> Date/Time: 2014-03-24 09:51:22.144 -0600
> OS Version: Mac OS X 10.9.2 (13C64)
> Report Version: 11
> Anonymous UUID: B8CEBD31-8387-ADD1-43BC-0723473B05E9
>
> Sleep/Wake UUID: 381143E4-3E75-48A3-A73B-792E98AC0FE8
>
> Crashed Thread: 0 Dispatch queue: com.apple.main-thread
>
> Exception Type: EXC_CRASH (SIGABRT)
> Exception Codes: 0x0000000000000000, 0x0000000000000000
>
> Application Specific Information:
> terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
> abort() called
>
>
> ------
>
> NOTES
>
> Happens only when working remotely (using FileMaker 12 Server Advanced), does not crash when I'm using a copy of the database on the local computer
>
> Doesn't occur at all on Windows 7 / FileMaker Pro Advanced 12.0v4
>
> FIXES
>
> My only solution is to re-write the scripts to not use the 'New Window' and 'Close Window' steps so much. But any other advice would be appreciated.
>
> From reading the Console it seems to be some type of error with memory allocation, but I don't fully understand the messages.
>
> Cheers,
>
> Mike
> _______________________________________________
> FMPexperts mailing list
> FMPexperts-YhOVfwX2n+***@public.gmane.org
> http://lists.ironclad.net.au/listinfo.cgi/fmpexperts-ironclad.net.au

Samuel Herschbein

2014-03-25 21:30:35 UTC

Permalink

Mike->

FileMaker has accepted negative window coordinates for me in OS X for years. I just tried in 13 on Mountain Lion, I opened an 800x800 window at -1000x-1000, it was fully off screen and behaved as expected (responded to command-W).

Sam

Post by Michael MacKinnon
Thanks for the feedback Sam!
Since this only happens over the Internet/WAN I think what you're saying is right. It could be that the content inside the windows are perhaps not rendering fast enough which is causing issues. A small delay should solve this (since the issue doesn't show up on the local machine or even over a LAN).
With Windows I can open the windows off screen but with OS X it always seems to draw them at 0,0 (doesn't accept negative values) so they remain visible.
Cheers,
Mike
Mike- >
I don't have a definitive answer, but some conjectures and long-shot suggestions.
OS X has had major window focus issues since Snow Leopard, windows don't get focus when they should and vice-versa. Most commonly people have windows where you can't click or control them. The only way to get them to respond is to minimize them from the Window menu and then select them from the Window menu.
My conjecture is the _CGSLockWindow errors are related to the window focus: OS X is trying to work with the wrong window (or no window...). This could be causing the CoreAnimation memory allocation fails.
What I would try: open the windows off-screen so the window manager doesn't have to try and display them. It may also help to put a short delay after creating a window to give the OS time to settle down.
Sam

Post by Michael MacKinnon
2014-03-24 09:51:16.444 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window

2014-03-24 09:51:16.444 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.445 FileMaker Pro[18667]: CoreAnimation: failed to allocate 11041024 bytes
2014-03-24 09:51:16.447 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.447 FileMaker Pro[18667]: _CGSLockWindow: Unable to lock window
2014-03-24 09:51:16.580 FileMaker Pro[18667]: CoreAnimation: failed to allocate 11041024 bytes

Post by Michael MacKinnon
2014-03-24 09:51:16.923 FileMaker Pro[18667]: FileMaker Pro(18667,0xa17c71a8) malloc: *** mach_vm_map(size=11042816) failed (error code=3)

*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug

Post by Michael MacKinnon
2014-03-24 09:51:17.433 FileMaker Pro[18667]: CGSImageDataLock: Cannot allocate memory