Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Sudden Logging out

balkyny

balkyny

macrumors member
Original poster
Jan 25, 2022
41
0
New York
Hi

Wanted to ask about this for a long time; I do not know what it is,but in the middle of working the screen goes black for a second and I am at the login choices. Then, I enter a password and it logs you in. All the windows, apps that were previously open, start to open.

But the work was gone. THere was no chance to save it.

I can't figure out what this is. I tried to reinstal high sierra 2 times. I can't find logic in this behavior. I work in sound program then open browser and start to type an address then boom - login screen. I tried to find something in system log, but did not know for what I am looking.

Automatic logoff is disabled. I tried enabling it with settings like 999 minutes of inactivity... same!

Any ideas?
 

Attachments

  • Screen Shot 2022-02-05 at 01.43.43.png
    Screen Shot 2022-02-05 at 01.43.43.png
    26 KB · Views: 252
Last edited:
balkyny said:
Hi

Wanted to ask about this for a long time; I do not know what it is,but in the middle of working the screen goes black for a second and I am at the login choices. Then, I enter a password and it logs you in. All the windows, apps that were previously open, start to open.

But the work was gone. THere was no chance to save it.

I can't figure out what this is. I tried to reinstal high sierra 2 times. I can't find logic in this behavior. I work in sound program then open browser and start to type an address then boom - login screen. I tried to find something in system log, but did not know for what I am looking.

Automatic logoff is disabled. I tried enabling it with settings like 999 minutes of inactivity... same!

Any ideas?
Click to expand...
That would be loginwindow crashing. I’ve had a lot that with Monterey sadly. Can you update past the version you’re at?
 
barbu said:
That would be loginwindow crashing. I’ve had a lot that with Monterey sadly. Can you update past the version you’re at?
Click to expand...
Seriously? This is what it is called? But login window is fine, the crash happens when already logged in and work in progress.

I never had this problem in OS X Yosemite. I am not sure what would happen if I take another step forward. Something may stop working
 
If you did upgrade to Mojave you would need a Metal supported GPU.

Have you looked in Console after re-logging in to see what flags up?
 
MarkC426 said:
If you did upgrade to Mojave you would need a Metal supported GPU.

Have you looked in Console after re-logging in to see what flags up?
Click to expand...

OK, then I cannot upgrade to Mojave :(

When you say FLAGS UP you mean in DEVICES section of console? I see yellow dots and red even. Is it what you mean? I never looked there before. GOOD I KNOW NOW. I usually looked in the syslogs trying to figure out how to interpret that information. no luck

So far I see:
attached images
 

Attachments

  • Screen Shot 2022-02-05 at 14.13.21.png
    Screen Shot 2022-02-05 at 14.13.21.png
    18.8 KB · Views: 112
  • Screen Shot 2022-02-05 at 14.14.05.png
    Screen Shot 2022-02-05 at 14.14.05.png
    17.4 KB · Views: 111
  • Screen Shot 2022-02-05 at 14.15.10.png
    Screen Shot 2022-02-05 at 14.15.10.png
    22.2 KB · Views: 96
  • Screen Shot 2022-02-05 at 14.16.36.png
    Screen Shot 2022-02-05 at 14.16.36.png
    26.5 KB · Views: 125
  • Screen Shot 2022-02-05 at 14.17.38.png
    Screen Shot 2022-02-05 at 14.17.38.png
    24.7 KB · Views: 105
balkyny said:
Seriously? This is what it is called? But login window is fine, the crash happens when already logged in and work in progress.

I never had this problem in OS X Yosemite. I am not sure what would happen if I take another step forward. Something may stop working
Click to expand...
Yes I understand. And yeah I believe that’s the name of the process. When it crashes, it restarts and that means going back to the login screen.
It’s just like “re-springing” in iOS, if you’ve seen that before.
 
Thanks. I will review this now. I also found someting. Check it out.

***********


There is no point in trying the vague 'catch all' solutions like wiping NVRAM and system controllers. The problem you are having is a SIGSEGV, or, a segmentation fault in WindowServer. It is likely due to corrupt identifiers. Those identifiers are stored in multiple places, and if enough get corrupt, you get crashes. While some identifiers are stored in the NVRAM (or PRAM), wiping this usually only postpones the next crash since the identifier eventually ends up in there again.
If WindowServer crashes, all GUI applications stop and it restarts via launchd. When WindowServer starts, it first gives you the login window. So in fact, you are not getting logged out, but your whole graphical session simply crashes.
Having a peek at your crash report, it seems this thread is crashing:
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

The last few calls were to color space functions (or methods), leading me to believe you might simply be dealing with a corrupt ICC profile.
The cash is within com.apple.CoreGraphics, and the most recent calls are to:
color_space_get_md5_digest + 57
color_space_get_identifier + 9
CGXColorSpaceRegistryCopyRegisteredColorSpace + 42
_CGXCopyColorSpace + 27
_XCopyColorSpace + 57

Now, if I'm right, it's trying to calculate the MD5 hash of a color space. It's doing that because it wants to find the identifier for a color space, and it needs that identifier because CGXColorSpaceRegistryCopyRegisteredColorSpace needs the color space data for the preset color profile for your monitor. Now, to be 100% this is the source of your crashes, I would need as many of your crash reports as possible, because if they all crash because of different reasons, it has nothing to do with the software on your system but it's more likely to be a hardware issue where bogus data is fed in to the software which then tries to do something with that data which it cannot do and therefore cashes.
A simple test might be to start Apple's built in ColorSync Utility and pressing the Repair button. This could print something like:
Header message digest (MD5) is not correct. Fixed.

Which would make sense since a broken MD5 might be the source of your crash. So try that first. On my system, that ColorSync Utility is in /Applications/Utilities and I think it has been there since every version of OS X. Please let me know if that found broken ICC files and if it could fix them. If not (either nothing found or unable to fix) please do post any crash logs on WindowServer you have :)
 
Right after this crash I found rgis error log. Perhaps someone can figure out what it is?

Process: WindowServer [171]
Path: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer
Identifier: WindowServer
Version: 600.00 (312.103.12)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Responsible: WindowServer [171]
User ID: 88

Date/Time: 2022-03-22 00:52:04.339 -0400
OS Version: Mac OS X 10.13.6 (17G14033)
Report Version: 12
Anonymous UUID: 2238E50B-89A1-F577-DD79-146EF8F04260


Time Awake Since Boot: 14000 seconds

System Integrity Protection: disabled

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000104
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0x104:
-->
__TEXT 0000000108782000-0000000108783000 [ 4K] r-x/rwx SM=COW ` [/System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/Resources/WindowServer]

Application Specific Information:
StartTime:2022-03-21 20:44:12
GPU:
MetalDevice for accelerator(0x3603): 0x7fe622e03398 (MTLDevice: 0x0)
MetalDevice for accelerator(0x4b07): 0x7fe622f1c308 (MTLDevice: 0x0)
IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IOU1@7/IOPP/PXS2@0/ATY,Hoolock@0/ATY_Hoolock
IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IOU0@3/IOPP/PXS1@0/ATY,Hoolock@0/ATY_Hoolock
IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IOU0@3/IOPP/PXS1@0/ATY,Hoolock@1/ATY_Hoolock

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libGPUSupportMercury.dylib 0x00007fff451913a0 gpumRestoreTextureData + 76
1 libGFXShared.dylib 0x00007fff3604e6d9 gfxUploadPluginTextureLevel + 111
2 GLEngine 0x00007fff36d0d5e7 gleSynchronizePluginTextureLevels + 279
3 GLEngine 0x00007fff36cd7aaf gleBindFramebuffer + 321
4 GLEngine 0x00007fff36c2055c glBindFramebuffer_Exec + 142
5 com.apple.SkyLight 0x00007fff4e44d33b CaptureSurfaceGL::populate(WSCompositeSourceLayer*) + 35
6 com.apple.SkyLight 0x00007fff4e563636 WSCALayerBackingUpdateFlatteningIfNeeded + 1345
7 com.apple.SkyLight 0x00007fff4e4ec1eb CGXNextSurface + 3246
8 com.apple.SkyLight 0x00007fff4e591209 generate_layers_for_window_surfaces(CGXRedrawState*, CGXWindow*, CGSOrderOp, unsigned int, int*, WSCompositeSourceLayer**, CGSRegionObject*) + 5581
9 com.apple.SkyLight 0x00007fff4e58bc9e generate_layers_for_window(CGXRedrawState*, CGXWindow*) + 3193
10 com.apple.SkyLight 0x00007fff4e589fb9 CGXUpdateDisplay + 13505
11 com.apple.SkyLight 0x00007fff4e58687a update_display_callback(void*, double) + 257
12 com.apple.SkyLight 0x00007fff4e5cd552 run_timer_pass + 495
13 com.apple.SkyLight 0x00007fff4e5fb1c9 CGXRunOneServicesPass + 247
14 com.apple.SkyLight 0x00007fff4e5fbd84 SLXServer + 832
15 WindowServer 0x0000000108782dde 0x108782000 + 3550
16 libdyld.dylib 0x00007fff5467d015 start + 1

Thread 1:
0 libsystem_kernel.dylib 0x00007fff547c41fa mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff547c3714 mach_msg + 60
2 com.apple.CoreDisplay 0x00007fff2c5ce685 0x7fff2c51f000 + 718469
3 com.apple.CoreDisplay 0x00007fff2c5ce813 0x7fff2c51f000 + 718867
4 libsystem_pthread.dylib 0x00007fff54995661 _pthread_body + 340
5 libsystem_pthread.dylib 0x00007fff5499550d _pthread_start + 377
6 libsystem_pthread.dylib 0x00007fff54994bf9 thread_start + 13

Thread 2:: com.apple.coreanimation.render-server
0 libsystem_kernel.dylib 0x00007fff547c41fa mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff547c3714 mach_msg + 60
2 com.apple.QuartzCore 0x00007fff37a22e62 CA::Render::Server::server_thread(void*) + 870
3 com.apple.QuartzCore 0x00007fff37a22ae6 thread_fun + 25
4 libsystem_pthread.dylib 0x00007fff54995661 _pthread_body + 340
5 libsystem_pthread.dylib 0x00007fff5499550d _pthread_start + 377
6 libsystem_pthread.dylib 0x00007fff54994bf9 thread_start + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fff547ce28a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff54995009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff54994be9 start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fff547ce28a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff54995009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff54994be9 start_wqthread + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000080
rdi: 0x00007fe627800600 rsi: 0x0000000000000000 rbp: 0x00007ffee747c3e0 rsp: 0x00007ffee747c3a0
r8: 0x0000000000000000 r9: 0x00000001166c5c3c r10: 0x0000000000000003 r11: 0x0000000000000206
r12: 0x00007fe627800600 r13: 0x00007fe624620b00 r14: 0x0000000000000000 r15: 0x00007fe613098e28
rip: 0x00007fff451913a0 rfl: 0x0000000000010246 cr2: 0x0000000000000104

Logical CPU: 0
Error Code: 0x00000004
Trap Number: 14
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back