Mac app suddenly stops displaying

Targets macOS
1

I am at a total loss with Check Writer. All the sudden today, when I run, the app starts, but never shows the main window. No matter how long I wait.

I thought it was code I had added today, so I went to projects that are already in the MAS and work fine, same result. I finally have to kill the app.

Here is what I get in Console :

Sep 4 19:53:46 Mitchs-iMac WindowServer[222]: common_reenable_update: UI updates were finally reenabled by application "CheckWriterIII.debug" after 105.54 seconds [0.01fps] (server forcibly re-enabled them after 1.00 seconds [1.00fps]) Sep 4 19:58:00 Mitchs-iMac CheckWriterIII.debug[3339]: MiniMenu.OpenTimer False Sep 4 19:58:01 Mitchs-iMac WindowServer[222]: disable_update_timeout: UI updates were forcibly disabled by application "CheckWriterIII.debug" for over 1.00 seconds. Server has re-enabled them. Sep 4 19:58:15 Mitchs-iMac WindowServer[222]: disable_update_likely_unbalanced: UI updates still disabled by application "CheckWriterIII.debug" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call. Sep 4 19:59:30 Mitchs-iMac kernel[0]: process CheckWriterIII.d[3339] thread 352519 caught burning CPU! It used more than 50% CPU (Actual recent usage: 98%) over 180 seconds. thread lifetime cpu usage 90.131831 seconds, (36.167364 user, 53.964467 system) ledger info: balance: 90007655744 credit: 90011130430 debit: 3474686 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 90951431471 Sep 4 19:59:34 Mitchs-iMac spindump[542]: Saved cpu_resource.diag report for CheckWriterIII.debug version 3.10 (3.1.0.3.0) to /Library/Logs/DiagnosticReports/CheckWriterIII.debug_2016-09-04-195934_Mitchs-iMac.cpu_resource.diag Sep 4 20:00:38 Mitchs-iMac com.apple.xpc.launchd[1] (com.matchsoftware.checkwriterIII.5986592[3339]): Service exited due to signal: Terminated: 15 Sep 4 20:00:41 Mitchs-iMac spindump[542]: Saved hang report for CheckWriterIII.debug version ??? (???) to /Library/Logs/DiagnosticReports/CheckWriterIII.debug_2016-09-04-200041_Mitchs-iMac.hang Sep 4 20:02:51 Mitchs-iMac WindowServer[222]: disable_update_timeout: UI updates were forcibly disabled by application "CheckWriterIII.debug" for over 1.00 seconds. Server has re-enabled them. Sep 4 20:03:05 Mitchs-iMac WindowServer[222]: disable_update_likely_unbalanced: UI updates still disabled by application "CheckWriterIII.debug" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call. Sep 4 20:04:20 Mitchs-iMac kernel[0]: process CheckWriterIII.d[3747] thread 384275 caught burning CPU! It used more than 50% CPU (Actual recent usage: 99%) over 180 seconds. thread lifetime cpu usage 90.106506 seconds, (36.938072 user, 53.168434 system) ledger info: balance: 90004264146 credit: 90007521347 debit: 3257201 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 90585055689 Sep 4 20:04:23 Mitchs-iMac spindump[542]: Saved cpu_resource.diag report for CheckWriterIII.debug version 3.08 (3.0.8.3.0) to /Library/Logs/DiagnosticReports/CheckWriterIII.debug_2016-09-04-200423_Mitchs-iMac.cpu_resource.diag

Any idea ?

2

I wondered if it was not a situation where the cache needs to be cleaned. How do I do that on Mac ?

OK. Found it : /Users//Library/Caches/Xojo

3

No. Clearing the cache did not do it. My Mac is haunted :frowning:

4

First I’d put a “Break” statement in line 1 in App.Constructor to see if I get there at all.
If I would get into the constructor, I’d be cheering hooray and start debugging.
If I would not get there (which is more likely), I’d create a new user account, and I’d try to run the compiled app.
If the compiled app runs fine, I’d start Xojo and run the app in debug mode.

And if your app uses plists or other preference files, delete them and have the application re-create them.

5

OK. There is definitely something wrong on that particular Mac. Not the project.

The same project runs perfectly in a VM.

I am going to restore my last disk clone.

6

Might Gatekeeper or xProtect interfer? Silent update of the signatures?

7

[quote=285316:@Michel Bujardet]I am at a total loss with Check Writer. All the sudden today, when I run, the app starts, but never shows the main window. No matter how long I wait.

[/quote]

Could you grab ‘/Library/Logs/DiagnosticReports/CheckWriterIII.debug_2016-09-04-195934_Mitchs-iMac.cpu_resource.diag’ and upload it somewhere accessible? Perhaps Pastebin?

8

I frankly don’t care what is causing this stupid circumstance. One minute my app was running, a few minutes later not only that project was not displaying anything anymore, but all previous projects including 5 or 6 versions prior that have gone in the MAS without a peep.

I strongly suspect some bizarre failing in Xojo.

Soon enough the drive will be back to its own self before the nasty bug.

9

Okay, so according to the console log; basically something when the window opens is holding up the process.

I get simile messages when re-opening complex Windows when the initial calibration of the content takes some time (i.e. Opening a very large image that the user selected last time).

10

OK. Thanks all. I decided yesterday I had suffered enough, and reinstated my last backup. Sure enough, now the app displays as it always did, even with the very last project.

If it had been a PC, I could have blamed the antivirus, or the infamous tendency of Windows for gremlins. But on a Mac, it is the very first time I experience such a huge glitch. I was feeling violated and hurt.

Sorry Joe, will never know what happened exactly. I just noticed your message this morning. Now I just pray for it never to happen again.

11

Or maybe the main window was placed outside the physical screen estate. That’s something I encountered ones.

12

I doubt it very much that was it. I place the window center Screen(0) in its open. But I will keep this in mind. Thanks.

13

The macOS is the new Windows, since Yosie, many weird and unexplained glitches happen, often restarting the machine makes them go away. Long gone are the days of months on months up times.

14

You can accomplish the same thing by changing the window placement in the properties of the window, setting it to main screen will have the same effect (without code).