I am using phantomjs docker container, latest version of wernight/phantomjs. Here is link. https://hub.docker.com/r/wernight/phantomjs/
The problem is; When I start the container, after some time (2-3 days)
container is stopping suddenly with below error. Anyone has any idea or suggestion ? I use exist container as is.
ERROR - 2017-08-29T05:26:36.534Z] RouterReqHand - _handle.error -
{"stack":"evaluateJavaScript#[native code]\nevaluate#phantomjs://platform/webpage.js:390:39\n_getTextCommand#phantomjs://code/webelement_request_handler.js:341:90\n_handle#phantomjs://code/webelement_request_handler.js:102:28\n_reroute#phantomjs://code/session_request_handler.js:61:20\n_handle#phantomjs://code/session_request_handler.js:120:42\n_reroute#phantomjs://code/request_handler.js:61:20\n_handle#phantomjs://code/router_request_handler.js:78:46","line":390,"sourceURL":"phantomjs://platform/webpage.js"}
phantomjs://platform/console++.js:263 in error
1 0x1b67967 phantomjs() [0x1b67967]
2 0x1b800a9 phantomjs() [0x1b800a9]
3 0x92035b phantomjs() [0x92035b]
4 0x13b9e20 phantomjs() [0x13b9e20]
5 0x13b9f2a phantomjs() [0x13b9f2a]
6 0x13bb9c1 phantomjs() [0x13bb9c1]
7 0x13bcaa4 phantomjs() [0x13bcaa4]
8 0x13bcb6c phantomjs() [0x13bcb6c]
9 0x97bf27 phantomjs() [0x97bf27]
10 0x77e64b phantomjs() [0x77e64b]
11 0x478dc4 phantomjs() [0x478dc4]
12 0x47ad10 phantomjs() [0x47ad10]
13 0x42d613 phantomjs() [0x42d613]
14 0x425e34 phantomjs() [0x425e34]
15 0x41b90c phantomjs() [0x41b90c]
16 0x46ba0b phantomjs() [0x46ba0b]
17 0x46c503 phantomjs() [0x46c503]
18 0x7b6cad phantomjs() [0x7b6cad]
19 0x17fd966 phantomjs() [0x17fd966]
20 0x19db06e phantomjs() [0x19db06e]
21 0x19e7b07 phantomjs() [0x19e7b07]
22 0x19eed55 phantomjs() [0x19eed55]
PhantomJS has crashed. Please read the bug reporting guide at
<http://phantomjs.org/bug-reporting.html and file a bug report.
Hard to say what is happening. You can run your container with --restart=unless-stopped. This will restart the container when it fails.
And since PhantomJS is no more maintained no one will answer your crash report on the forum. So best to just recover from the issue when it happens
Related
I have a process Id in windows Machine, I need to write a Power-shell script to check whether this process is running as docker container or not.
Being a newbie ,I am not able to find anything straight forward how to check it.
I have tried this by expanding the suggestion to use docker inspect.
Here's the whole config:
PS C:\Users\Microsoft> docker inspect -f '{{.State.Pid}}' 8b2f6493d26e
4492
The command above returned the ID on which the container is instantiated.
PS C:\Users\Microsoft> Get-Process -Id 4492 | select si
SI
--
6
Now, I can use the above to query the SI of the specific ID returned previously. You see that the SI for that Process ID is 6, so all processes on this container will be running on that SI. Now I can run:
PS C:\Users\Microsoft> Get-Process | Where-Object {$_.si -eq 6}
Handles NPM(K) PM(K) WS(K) CPU(s) Id SI ProcessName
------- ------ ----- ----- ------ -- -- -----------
83 6 976 4776 0.00 8380 6 CExecSvc
251 13 2040 6308 0.16 7308 6 csrss
38 6 792 3176 0.00 3772 6 fontdrvhost
793 20 3900 13688 0.44 8912 6 lsass
232 13 2624 10384 0.11 7348 6 msdtc
75 6 928 4872 0.02 4492 6 ServiceMonitor
213 10 2372 7008 0.27 8308 6 services
137 8 1496 6952 0.05 864 6 svchost
172 12 2656 9292 0.06 2352 6 svchost
110 7 1188 6084 0.03 2572 6 svchost
241 14 4616 12508 0.19 5460 6 svchost
817 30 12388 30824 9.73 6056 6 svchost
172 12 3984 11528 0.14 6420 6 svchost
405 16 7284 14284 0.25 6524 6 svchost
494 22 13480 29568 1.45 7060 6 svchost
509 38 5636 19432 0.30 7936 6 svchost
334 13 2776 10912 0.13 8604 6 svchost
122 8 3048 9180 0.19 8816 6 svchost
383 14 2392 8624 0.22 9080 6 svchost
232 19 5060 14284 0.13 9744 6 w3wp
155 11 1380 7276 0.05 5008 6 wininit
The above is the output of all processes running on my container host that match the SI 6. You can even see the w3wp process which is the IIS process running inside the container.
One note here is that this is only possible with Process isolation on Windows containers. Hyper-V containers won't have their processes shown on the host.
I am new at mobile development and Xamarin, trying to publish my first iOS app but,
Apple rejected my app due to this crash log :
OS Version: iPhone OS 13.6.1 (17G80)
Release Type: User
Baseband Version: n/a
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Thread 0 name: tid_407 Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x0000000185d02df0 0x185cdc000 + 159216
1 libsystem_pthread.dylib 0x0000000185c22948 0x185c20000 + 10568
2 libsystem_c.dylib 0x0000000185bb1c24 0x185b3c000 + 482340
3 libsystem_c.dylib 0x0000000185bb1bb0 0x185b3c000 + 482224
4 SpeedRead.iOS 0x000000010422b470 undefined
5 SpeedRead.iOS 0x0000000104220b90 _xamarin_get_block_descriptor
6 SpeedRead.iOS 0x00000001040e6590 _sqlite3_rekey_v2
7 SpeedRead.iOS 0x000000010407b3f0 _sqlite3_rekey_v2
8 SpeedRead.iOS 0x0000000104079dd8 _sqlite3_rekey_v2
9 SpeedRead.iOS 0x000000010406fbb8 _sqlite3_rekey_v2
10 SpeedRead.iOS 0x00000001025b66ac _sqlite3_rekey_v2
11 SpeedRead.iOS 0x000000010232635c _sqlite3_rekey_v2
12 SpeedRead.iOS 0x000000010232db84 _sqlite3_rekey_v2
13 SpeedRead.iOS 0x0000000102681d9c _sqlite3_rekey_v2
14 SpeedRead.iOS 0x0000000102576380 _sqlite3_rekey_v2
15 SpeedRead.iOS 0x000000010408cff0 _sqlite3_rekey_v2
16 SpeedRead.iOS 0x00000001041486a4 _sqlite3_rekey_v2
17 SpeedRead.iOS 0x000000010414bf08 _sqlite3_rekey_v2
18 SpeedRead.iOS 0x0000000102193a14 _sqlite3_rekey_v2
19 SpeedRead.iOS 0x0000000102194744 _sqlite3_rekey_v2
20 Foundation 0x0000000186320f94 0x1861df000 + 1318804
21 CoreFoundation 0x0000000185e96d14 0x185dea000 + 707860
22 CoreFoundation 0x0000000185e96c68 0x185dea000 + 707688
23 CoreFoundation 0x0000000185e963c4 0x185dea000 + 705476
24 CoreFoundation 0x0000000185e911fc 0x185dea000 + 684540
25 CoreFoundation 0x0000000185e90bc8 0x185dea000 + 682952
26 GraphicsServices 0x00000001902725cc 0x19026f000 + 13772
27 UIKitCore 0x000000018a043744 0x1895d5000 + 10938180
28 SpeedRead.iOS 0x00000001026cc238 _sqlite3_rekey_v2
29 SpeedRead.iOS 0x0000000102635ef0 _sqlite3_rekey_v2
30 SpeedRead.iOS 0x0000000102635e74 _sqlite3_rekey_v2
31 SpeedRead.iOS 0x00000001021b9f64 _sqlite3_rekey_v2
32 SpeedRead.iOS 0x0000000102576380 _sqlite3_rekey_v2
33 SpeedRead.iOS 0x000000010408cff0 _sqlite3_rekey_v2
34 SpeedRead.iOS 0x00000001041486a4 _sqlite3_rekey_v2
35 SpeedRead.iOS 0x000000010414e8fc _sqlite3_rekey_v2
36 SpeedRead.iOS 0x000000010406b5a8 _sqlite3_rekey_v2
37 SpeedRead.iOS 0x0000000104228594 undefined
38 SpeedRead.iOS 0x00000001021b9ebc _sqlite3_rekey_v2
39 libdyld.dylib 0x0000000185d0d384 0x185d0c000 + 4996
I can't reproduce this crash at visual studio, i tried with all simulators but it works fine. Apple review says :
Buttons open pages which is reading database with entity framework and sqllite.
( here is soure code : https://github.com/fatihmgenc/SpeedRead , pages are AntrenmanPage & MetinEklemePage )
I use Ad-hoc for upload app to store-connect and my build settings :
What do you suggest me at this point ?
There's an issue with your SQLite database, as you can see it says that the _sqlite3_rekey_v2 is undefined. Most likely when you tested before submission, you forgot to delete the app from your device, along with the your cache and the temp files on the computer.
If you follow the buttons clicks to what they are saying, the bug is in the Antrenman page, and it's related to your SQLite database, so it could be in this line or in this line. So try to place a try-catch around those two lines and inside the catch, tell the code what it should do when the previous line was not called.
I started a new ruby-on-rails project called "myrubyblog", changed directories to my project then launched rails server command, but the terminal then outputs me this after an incredible amount of lines of information I don't understand;
-- Other runtime information -----------------------------------------------
* Loaded script: bin/rails
* Loaded features:
0 enumerator.so
1 thread.rb
2 rational.so
3 complex.so
4 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/armv7l-linux-eabihf/enc/encdb.so
5 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/armv7l-linux-eabihf/enc/trans/transdb.so
6 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/armv7l-linux-eabihf/rbconfig.rb
7 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/compatibility.rb
8 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/defaults.rb
9 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/deprecate.rb
10 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/errors.rb
11 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/version.rb
12 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/requirement.rb
13 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/platform.rb
14 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/basic_specification.rb
15 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/stub_specification.rb
16 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/util/list.rb
17 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/armv7l-linux-eabihf/stringio.so
18 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri/rfc2396_parser.rb
19 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri/rfc3986_parser.rb
20 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri/common.rb
21 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri/generic.rb
22 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri/ftp.rb
23 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri/http.rb
24 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri/https.rb
25 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri/ldap.rb
26 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri/ldaps.rb
27 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri/mailto.rb
28 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/uri.rb
29 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/specification.rb
30 /home/pi/.rvm/rubies/ruby-2.5.1/lib/ruby/2.5.0/rubygems/exceptions.rb
... (up to 320 lines)
[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html
Abandon
What is that supposed to mean?
Note: I have been using Xcode7.x with MacOS Sierra since Beta 1 or 2. It's worked just fine. I haven't touched Xcode 8 on this machine.
Since beta 5, suddenly I can't do anything with Xcode 7. I start it up and open my workspace and as soon as I change the view to another file or project or assets or anything, it crashes with the following error:
Process: Xcode [869]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 7.3.1 (10188.1)
Build Info: IDEFrameworks-10188001000000000~3
App Item ID: 497799835
App External ID: 817226719
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Xcode [869]
User ID: 501
Date/Time: 2016-08-11 11:21:13.167 -0700
OS Version: Mac OS X 10.12 (16A286a)
Report Version: 12
Anonymous UUID: BC13DBAB-4D04-3E83-CF4A-4F1FFB581BCE
Time Awake Since Boot: 250 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0x20:
-->
__TEXT 000000010ce99000-000000010ce9d000 [ 16K] r-x/rwx SM=COW /Applications/Xcode.app/Contents/MacOS/Xcode
Application Specific Information:
ProductBuildVersion: 7D1014
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff8ce08a31 objc_retain + 33
1 com.apple.dt.DVTKit 0x000000010d73838a __38-[DVTSourceTextView setTextContainer:]_block_invoke + 28
2 com.apple.dt.DVTFoundation 0x000000010d0e5e88 __95-[NSObject(DVTObservingConvenience) _dvt_newObserverForKeyPath:options:owner:withHandlerBlock:]_block_invoke + 91
3 com.apple.dt.DVTFoundation 0x000000010d0e4d2e __73-[DVTObservingBlockToken observeValueForKeyPath:ofObject:change:context:]_block_invoke.195 + 83
4 com.apple.dt.DVTFoundation 0x000000010d00b911 DVTInvokeWithStrongOwnership + 75
5 com.apple.dt.DVTFoundation 0x000000010d0e48c6 -[DVTObservingBlockToken observeValueForKeyPath:ofObject:change:context:] + 336
6 com.apple.Foundation 0x00007fff7a0e9dbd NSKeyValueNotifyObserver + 350
7 com.apple.Foundation 0x00007fff7a0e9654 NSKeyValueDidChange + 486
8 com.apple.Foundation 0x00007fff7a2282d7 -[NSObject(NSKeyValueObservingPrivate) _changeValueForKeys:count:maybeOldValuesDict:usingBlock:] + 944
9 com.apple.Foundation 0x00007fff7a0ad3c9 -[NSObject(NSKeyValueObservingPrivate) _changeValueForKey:key:key:usingBlock:] + 60
10 com.apple.Foundation 0x00007fff7a115c3b _NSSetObjectValueAndNotify + 261
11 com.apple.CoreFoundation 0x00007fff786cfde7 -[NSArray makeObjectsPerformSelector:withObject:] + 279
12 com.apple.UIFoundation 0x00007fff8ac9282b -[NSLayoutManager setTextStorage:] + 912
13 com.apple.dt.DVTKit 0x000000010d6ad401 -[DVTFoldingLayoutManager setTextStorage:] + 154
14 com.apple.UIFoundation 0x00007fff8ace6515 -[NSTextStorage dealloc] + 117
15 com.apple.dt.DVTKit 0x000000010d64647e -[DVTTextStorage dealloc] + 911
16 com.apple.Foundation 0x00007fff7a11dcbd NSKVODeallocate + 94
17 com.apple.AppKit 0x00007fff76627281 -[NSTextView dealloc] + 813
18 com.apple.dt.DVTKit 0x000000010d803030 -[DVTCompletingTextView dealloc] + 120
19 com.apple.AppKit 0x00007fff76427a96 -[NSTextView release] + 464
20 libsystem_blocks.dylib 0x00007fff8d728952 _Block_release + 102
21 libsystem_blocks.dylib 0x00007fff8d728952 _Block_release + 102
22 libdispatch.dylib 0x00007fff8d6d9c6f _dispatch_source_handler_dispose + 23
23 libdispatch.dylib 0x00007fff8d6c9da3 _dispatch_source_cancel_callout + 90
24 libdispatch.dylib 0x00007fff8d6c0a6e _dispatch_source_invoke + 1512
25 libdispatch.dylib 0x00007fff8d6cba0f _dispatch_main_queue_callback_4CF + 505
26 com.apple.CoreFoundation 0x00007fff7870bd39 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
27 com.apple.CoreFoundation 0x00007fff786cd15d __CFRunLoopRun + 2205
28 com.apple.CoreFoundation 0x00007fff786cc664 CFRunLoopRunSpecific + 420
29 com.apple.HIToolbox 0x00007fff77c6ef7c RunCurrentEventLoopInMode + 240
30 com.apple.HIToolbox 0x00007fff77c6edb1 ReceiveNextEventCommon + 432
31 com.apple.HIToolbox 0x00007fff77c6ebe6 _BlockUntilNextEventMatchingListInModeWithFilter + 71
32 com.apple.AppKit 0x00007fff76365c41 _DPSNextEvent + 1093
33 com.apple.AppKit 0x00007fff76a75693 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1637
34 com.apple.dt.DVTKit 0x000000010d601439 -[DVTApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 396
35 com.apple.AppKit 0x00007fff7635a610 -[NSApplication run] + 926
36 com.apple.AppKit 0x00007fff763250e2 NSApplicationMain + 1237
37 com.apple.dt.Xcode 0x000000010ce9a39b 0x10ce99000 + 5019
38 libdyld.dylib 0x00007fff8d6f4255 start + 1
Anyone else come across this in beta 5?
From macOS Sierra beta 5 release notes:
Xcode
Xcode 7.3.1 is not compatible with macOS Sierra.
Workaround: Use Xcode 8.0 beta or later when running on macOS Sierra.
It should be possible to use swift 2.3 in xcode 8. From beta 6 notes:
For developers on macOS Sierra it is recommended that you move to Xcode 8. You can continue to develop with the Swift 2.x release with the included Swift 2.3 compiler until you are ready to migrate to Swift 3. Xcode 7.3.1 is not supported on macOS Sierra. (27224895)
With a stable Mac OS X Sierra (v10.12), Xcode 7.3.1 started to work on third launch. Everything seems to work fine, no problems with emulator or anything!
Don't lose hope if Xcode doesn't work on the first launch :)
I've been able to recreate this same particular issue (DVTSourceTextView setTextContainer) in Mac OS Sierra (non beta) for xcode 7.3.1. Oddly, I found it somehow attributed to my Cocoapods implementation. I was able to open up the project but not the workspace. I deleted my workspace and Pods directory then did a pod install to redo it.
The issue was fixed then. Lost a couple days of work researching, hoping this helps someone.
I am developing an Application for iOS and I changed nothing in the Application. But at a restart of my Mac, Xcode crashes every time.
Don't know if this is important, but my spotlight can't find any applications and also when I open the finder and using the shortcut cmd + shift + H I see a white window.
Xcode isn't starting anymore and throws this error:
Process: Xcode [1346]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 7.2 (9548)
Build Info: IDEFrameworks-9548000000000000~7
App Item ID: 497799835
App External ID: 814662604
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Xcode [1346]
Date/Time: 2015-12-24 11:01:44.753 +0100
OS Version: Mac OS X 10.11.2 (15C50)
Report Version: 11
Time Awake Since Boot: 4000 seconds
System Integrity Protection: enabled
Crashed Thread: 4 Dispatch queue: DVTFilePathEventWatcher - event queue
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0:
-->
__TEXT 0000000108a5a000-0000000108a5e000 [ 16K] r-x/rwx SM=COW /Applications/Xcode.app/Contents/MacOS/Xcode
Application Specific Information:
ProductBuildVersion: 7C68
Thread 0:: Dispatch queue: DVTFilePath cache derivation lock for key DVTFilePathKey_SortedDirectoryContents
0 libobjc.A.dylib 0x00007fff8df27aa0 search_method_list(method_list_t const*, objc_selector*) + 2
1 libobjc.A.dylib 0x00007fff8df28d76 lookUpImpOrForward + 413
2 libobjc.A.dylib 0x00007fff8df22591 objc_msgSend + 209
3 com.apple.dt.DVTFoundation 0x0000000108a741f8 -[DVTFileSystemVNode addCachedEntriesFromDictionary:] + 215
4 com.apple.dt.DVTFoundation 0x0000000108bd2e2d __33-[DVTFilePath cachedValueForKey:]_block_invoke549 + 245
5 libdispatch.dylib 0x00007fff9fcbd33f _dispatch_client_callout + 8
6 libdispatch.dylib 0x00007fff9fcbe926 _dispatch_barrier_sync_f_invoke + 74
7 com.apple.dt.DVTFoundation 0x0000000108cd1005 DVTDispatchBarrierSync + 62
8 com.apple.dt.DVTFoundation 0x0000000108a69627 -[DVTDispatchLock performLockedBlock:] + 116
9 com.apple.dt.DVTFoundation 0x0000000108a715b0 -[DVTFilePath cachedValueForKey:] + 1802
10 com.apple.dt.DVTFoundation 0x0000000108a70afc -[DVTToolchainRegistry scanSearchPathAndRegisterToolchains:] + 563
11 com.apple.dt.IDEFoundation 0x00000001097d1a66 IDEInitialize + 655
12 com.apple.dt.IDEKit 0x0000000109ecdf7c -[IDEApplicationController applicationWillFinishLaunching:] + 708
13 com.apple.CoreFoundation 0x00007fffa18fa70c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
14 com.apple.CoreFoundation 0x00007fffa18fa67f ___CFXRegistrationPost_block_invoke + 63
15 com.apple.CoreFoundation 0x00007fffa18f9d47 _CFXRegistrationPost + 407
16 com.apple.CoreFoundation 0x00007fffa18f9ab2 ___CFXNotificationPost_block_invoke + 50
17 com.apple.CoreFoundation 0x00007fffa18f3d42 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1922
18 com.apple.CoreFoundation 0x00007fffa17e2145 _CFXNotificationPost + 693
19 com.apple.Foundation 0x00007fff9ef36921 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
20 com.apple.dt.DVTFoundation 0x0000000108c6cf55 -[NSNotificationCenter(DVTNSNotificationCenterAdditions) _dvt_postNotificationName:object:userInfo:] + 698
21 com.apple.AppKit 0x00007fff9db412c2 -[NSApplication finishLaunching] + 354
22 com.apple.dt.DVTKit 0x0000000109275f62 -[DVTApplication finishLaunching] + 149
23 com.apple.AppKit 0x00007fff9db40e05 -[NSApplication run] + 231
24 com.apple.AppKit 0x00007fff9dac3520 NSApplicationMain + 1176
25 libdyld.dylib 0x00007fff9a8605ad start + 1
Could this be an issue due to Permissions conflicts?
ANSWER:
After I changed the rights from my OSX-Drive to everyone can write&read. Everything worked. But I knew that this is a temporary solution, so I decided to reinstall my MAC and everything was fine.
Delete ~/Library/Developer/Xcode/DerivedData by running this command in terminal:
rm -r ~/Library/Developer/XCode/DerivedData
If that doesnt work, At this point and with given info, all I could recommend to delete and reinstall Xcode.
If the delete of ~/Library/Developer/Xcode/DerivedData is not working for you, try this steps to remove xcuserdata:
open a Finder window and navigate to your project
right-click on the .xcodeproj OR .xcworkspace file
select Show Package Contents
a new window appears
delete a folder called xcuserdata
I had one where i selected a file that was quite large which crashed xcode when it tried to parse it. Then when i restarted it somehow it got set to load that file on start. Only way i saw was to temporarily rename the file that it was trying to load at start so it would load empty.
I'll recommend deleting xcuserdata: folder from both of your .xcodeproj & .xcworkspace file (open with Show Package Contents) and try again.
I hope this will work.
Ensure there are no issues with your SPM packages/dependencies.
This is simply another suggestion. I just spent some time debugging this on a fairly popular open source project.
My Xcode first crashed when I updated a SPM package, so I was fairly certain it was an issue with one of the future commits in that package or a SPM bug. I subscribe to Occam's Razor, so I started going through the changes in the commits.
After some time, I found a duplicate Swift Playground page delcaration in contents.xcplayground. I removed that single line, pushed the PR, and everything worked fine after that.
To be able to reopen the project:
Open project.pbxproj in your code editor of choice (e.g. vi, nano, emacs, atom, code).
Remove the offending package or packages from the /* Begin XCRemoteSwiftPackageReference section */ and /* Begin XCSwiftPackageProductDependency section */ sections.
Save the file and Xcode should now open.
Again, if your Xcode is immediately crashing when opening a project (and you last updated/auto-updated a SPM package) go through your packages.