MonoDevelop在High Sierra(OSX 10.13)上崩溃

17

我在将系统更新到最新的macOS 10.13 beta并使用unity monoDevelop后,从昨天开始遇到了问题。以下是我收到的崩溃报告。

Process:               mono-sgen [9057]
Path:                  /tmp/*/mono
Identifier:            com.unity.monodevelop
Version:               5.9.6 (5.9.6)
Code Type:             X86 (Native)
Parent Process:        ??? [1]
Responsible:           mono-sgen [9057]
User ID:               501

Date/Time:             2017-06-15 11:43:09.345 +0530
OS Version:            Mac OS X 10.13 (17A264c)
Report Version:        12
Anonymous UUID:        ACA523AB-96B9-4E46-8D2A-A2210B9A181A

Sleep/Wake UUID:       5715E1CB-BBDF-4E3C-9CEE-8F8C01ADD64D

Time Awake Since Boot: 36000 seconds
Time Since Wake:       6400 seconds

System Integrity Protection: enabled

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

Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000d9d1efbd
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0xd9d1efbd:
    Stack                  00000000bf7ee000-00000000bffe5000 [ 8156K] rw-/rwx SM=COW  
--> 
    Submap                 00000000ffff0000-00000000ffff1000 [    4K] r--/r-- SM=PRV  process-only VM submap

Application Specific Information:
abort() called

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib          0xa7617f6a __pthread_kill + 10
1   libsystem_pthread.dylib         0xa77346dd pthread_kill + 307
2   libsystem_c.dylib               0xa756881e abort + 133
3   mono                            0x000dc435 mono_handle_native_sigsegv + 757
4   mono                            0x001282a2 mono_arch_handle_altstack_exception + 162
5   mono                            0x0002890e mono_sigsegv_signal_handler + 446
6   libsystem_platform.dylib        0xa7728fcb _sigtramp + 43
7   ???                             0xffffffff 0 + 4294967295
8   mono                            0x00028750 mono_sigill_signal_handler + 48
9   com.apple.Foundation            0x9524f536 _NSAddExceptionHandlerForLock + 21
10  com.apple.AppKit                0x9157d276 _NSAppKitLock + 78
11  com.apple.AppKit                0x913c4ecd -[NSApplication _addWindow:] + 50
12  com.apple.AppKit                0x913c47d0 -[NSWindow _commonInitFrame:styleMask:backing:defer:] + 295
13  com.apple.AppKit                0x913c33e9 -[NSWindow _initContent:styleMask:backing:defer:contentView:] + 940
14  com.apple.AppKit                0x9142ccaf -[NSPanel _initContent:styleMask:backing:defer:contentView:] + 67
15  com.apple.AppKit                0x913c3033 -[NSWindow initWithContentRect:styleMask:backing:defer:] + 72
16  com.apple.AppKit                0x9142cc5a -[NSPanel initWithContentRect:styleMask:backing:defer:] + 93
17  com.apple.AppKit                0x9142c426 -[NSWindowTemplate nibInstantiate] + 419
18  com.apple.AppKit                0x91386ee5 -[NSIBObjectData instantiateObject:] + 255
19  com.apple.AppKit                0x913866f8 -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 311
20  com.apple.AppKit                0x913865bc -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 37
21  com.apple.AppKit                0x9137e6b1 loadNib + 482
22  com.apple.AppKit                0x9137dbbc +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 289
23  com.apple.AppKit                0x91598719 +[NSBundle(NSNibLoadingInternal) _loadNibFile:externalNameTable:options:withZone:] + 129
24  com.apple.AppKit                0x9163b5fe +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 43
25  com.apple.AppKit                0x9163b5ac _NXLoadNib + 169
26  com.apple.AppKit                0x9163b09a -[NSAlert init] + 97
27  ???                             0x085cc138 0 + 140296504
28  ???                             0x0b13c470 0 + 185844848
29  ???                             0x0b13aa70 0 + 185838192
30  ???                             0x0b13a800 0 + 185837568
31  ???                             0x0b13a738 0 + 185837368
32  ???                             0x0b139f5c 0 + 185835356
33  ???                             0x0b13a065 0 + 185835621
34  mono                            0x0002b3ff mono_jit_runtime_invoke + 751
35  mono                            0x001ee13f mono_runtime_invoke + 127
36  mono                            0x001f4fcd mono_runtime_invoke_array + 941
37  mono                            0x001679d5 ves_icall_InternalExecute + 309
38  ???                             0x0a37f690 0 + 171439760
39  mscorlib.dll.dylib              0x019ac5b9 System_Runtime_Remoting_RemotingServices_InternalExecuteMessage_System_MarshalByRefObject_System_Runtime_Remoting_Messaging_IMethodCallMessage + 521
40  mscorlib.dll.dylib              0x01999865 System_Runtime_Remoting_Messaging_StackBuilderSink_SyncProcessMessage_System_Runtime_Remoting_Messaging_IMessage + 245
41  mscorlib.dll.dylib              0x01999424 System_Runtime_Remoting_Messaging_ServerObjectTerminatorSink_SyncProcessMessage_System_Runtime_Remoting_Messaging_IMessage + 132
42  mscorlib.dll.dylib              0x01989230 System_Runtime_Remoting_Lifetime_LeaseSink_SyncProcessMessage_System_Runtime_Remoting_Messaging_IMessage + 64
43  ???                             0x0b139e9a 0 + 185835162
44  ???                             0x0b139e2c 0 + 185835052
45  ???                             0x0b139cf0 0 + 185834736
46  mscorlib.dll.dylib              0x019b083a System_Runtime_Remoting_ClientActivatedIdentity_SyncObjectProcessMessage_System_Runtime_Remoting_Messaging_IMessage + 154
47  mscorlib.dll.dylib              0x01999287 System_Runtime_Remoting_Messaging_ServerContextTerminatorSink_SyncProcessMessage_System_Runtime_Remoting_Messaging_IMessage + 423
48  mscorlib.dll.dylib              0x0198615f System_Runtime_Remoting_Contexts_CrossContextChannel_SyncProcessMessage_System_Runtime_Remoting_Messaging_IMessage + 239
49  mscorlib.dll.dylib              0x0198d577 System_Runtime_Remoting_Messaging_ClientContextTerminatorSink_SyncProcessMessage_System_Runtime_Remoting_Messaging_IMessage + 503
50  mscorlib.dll.dylib              0x0198eeb7 System_Runtime_Remoting_Messaging_EnvoyTerminatorSink_SyncProcessMessage_System_Runtime_Remoting_Messaging_IMessage + 55
51  mscorlib.dll.dylib              0x019a377a System_Runtime_Remoting_Proxies_RemotingProxy_Invoke_System_Runtime_Remoting_Messaging_IMessage + 970
52  mscorlib.dll.dylib              0x019a2164 System_Runtime_Remoting_Proxies_RealProxy_PrivateInvoke_System_Runtime_Remoting_Proxies_RealProxy_System_Runtime_Remoting_Messaging_IMessage_System_Exception__object___ + 1268
53  ???                             0x0a37f09f 0 + 171438239
54  mono                            0x0002b3ff mono_jit_runtime_invoke + 751
55  mono                            0x001ee13f mono_runtime_invoke + 127
56  mono                            0x001f78a1 mono_remoting_invoke + 145
57  mono                            0x001bc690 mono_remoting_wrapper + 192
58  ???                             0x0a37efd8 0 + 171438040
59  ???                             0x0b1396f0 0 + 185833200
60  ???                             0x0b139608 0 + 185832968
61  ???                             0x0b139248 0 + 185832008
62  ???                             0x0b13913c 0 + 185831740
63  ???                             0x0b1390e0 0 + 185831648
64  ???                             0x0b13802c 0 + 185827372
65  ???                             0x0333c154 0 + 53723476
66  ???                             0x005800a8 0 + 5767336
67  ???                             0x0057fe2c 0 + 5766700
68  ???                             0x0057ff07 0 + 5766919
69  mono                            0x0002b3ff mono_jit_runtime_invoke + 751
70  mono                            0x001ee13f mono_runtime_invoke + 127
71  mono                            0x001f41c1 mono_runtime_exec_main + 401
72  mono                            0x001f3f64 mono_runtime_run_main + 660
73  mono                            0x000a5e5d mono_jit_exec + 93
74  mono                            0x000a8130 mono_main + 7904
75  mono                            0x0001d730 main + 768
76  mono                            0x0001d425 start + 53

Thread 1:
0   libsystem_kernel.dylib          0xa760eeaa semaphore_wait_trap + 10
1   mono                            0x0027116a mono_sem_wait + 26
2   mono                            0x001ec05a finalizer_thread + 154
3   mono                            0x001ca065 start_wrapper + 517
4   mono                            0x002766b0 inner_start_thread + 240
5   libsystem_pthread.dylib         0xa773174d _pthread_body + 292
6   libsystem_pthread.dylib         0xa7731629 _pthread_start + 376
7   libsystem_pthread.dylib         0xa7730d02 thread_start + 34

Thread 2:
0   libsystem_kernel.dylib          0xa761878e __workq_kernreturn + 10
1   libsystem_pthread.dylib         0xa7731103 _pthread_wqthread + 1023
2   libsystem_pthread.dylib         0xa7730cde start_wqthread + 34



External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 2
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 89884
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=344.8M resident=0K(0%) swapped_out_or_unallocated=344.8M(100%)
Writable regions: Total=102.0M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=102.0M(100%)

                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
Activity Tracing                   256K        2 
CG image                          1032K        3 
CoreAnimation                       32K        6 
CoreUI image file                  168K        3 
Foundation                           4K        2 
Image IO                          1036K        4 
Kernel Alloc Once                    8K        2 
MALLOC                            55.9M       33 
MALLOC guard page                   48K       12 
Stack                             14.0M       17 
Stack Guard                       56.2M       17 
VM_ALLOCATE                       29.6M       56 
VM_ALLOCATE (reserved)             164K        6         reserved VM address space (unallocated)
__DATA                            13.7M      319 
__FONT_DATA                          4K        2 
__LINKEDIT                        88.2M       45 
__OBJC                            6616K      136 
__TEXT                           256.6M      318 
__UNICODE                          556K        2 
mapped file                      265.7M      259 
shared memory                      644K       12 
===========                     =======  ======= 
TOTAL                            790.1M     1235 
TOTAL, minus reserved VM space   790.0M     1235 

Model: MacBookPro9,2, BootROM MBP91.00D3.B21, 2 processors, Intel Core i5, 2.5 GHz, 12 GB, SMC 2.2f44
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x0198, 0x393930353432382D3432372E4130304C4620
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x0198, 0x393930353436392D3036332E4130304C4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (7.21.190.7.1a3)
Bluetooth: Version 6.0.0d40, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: APPLE HDD HTS545050A7E362, 500.11 GB
Serial ATA Device: HL-DT-ST DVDRW  GS41N
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: USB 3.0 Bus
USB Device: vivo Android Phone
Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1

我已经尝试过在monoDevelop.app的内容文件夹上设置了权限,并应用到了所有的子文件夹。


请阅读在什么情况下我可以在我的问题中添加“紧急”或其他类似短语,以便获得更快的答案? - 总结是这不是一个理想的方式来处理志愿者,并且可能会适得其反。请不要在您的问题中添加此内容。 - halfer
1
@halfer感谢您提到的观点。在未来发布任何问题之前,我将始终考虑这一点。 - Aman Kumar Aggarwal
不意外,因为你在一个预发布环境上运行。 - Lex Li
5个回答

18

我也遇到了这个问题。尝试删除你的MonoDevelop数据(此方法对我有效)。

打开终端并运行以下命令:

rm -rf ~/Library/Preferences/MonoDevelop-Unity-5.0

哇,我一直遇到这个问题,所以每周大约会重新查看一次这个答案。 - pookie
我安装了2017.2的最新补丁,但问题仍然存在,我不得不定期重新运行rm命令。 - David Airapetyan

8

更新(2018年2月):

截至2018年,Unity Technologies已经推荐使用 Visual Studio for Mac 作为Mac用户的首选编辑器。在所有那些红旗和警报告诉你逃跑之前,请注意VS/Mac是Xamarin Studio(由Microsoft收购)的分支,而Xamarin Studio是MonoDevelop的一个分支。

因为它是一个分支,所以VS/Mac只是MonoDevelop的更新版本,更加积极地维护,崩溃、内存泄漏和其他生产力瓶颈更少。在我过去一个月的使用中,VS/Mac非常稳定,其内存占用量也相当稳定,据我所知,没有明显的膨胀。

最后,VS/Mac有三个版本可用:Community,Professional和Enterprise。

您可以从http://visualstudio.com下载VS/Mac,下载和安装与安装MonoDevelop或Xamarin一样简单。

只需进入Unity首选项,选择VS/Mac作为您的外部代码编辑器,就可以开始了。

试试吧。


Unity已发布补丁以解决MonoDevelop崩溃问题。这些补丁适用于以下版本的Unity:

  • 2017.2
  • 2017.1
  • 5.6.3
  • 5.5.4
如果您使用的版本未列出,则可能需要更改Unity版本,回滚Mac OS X或使用Xamarin解决方法。
这是Unity修补程序的URL:
https://unity3d.com/unity/qa/patch-releases 这是有关更多信息的Unity论坛链接:
https://forum.unity.com/threads/unity-and-macos-10-13-high-sierra.474527/

2

我知道你更喜欢使用MonoDevelop,但你有尝试过带有Unity扩展的Visual Studio Code吗?虽然它不是完美的,但我尝试了一下后就再也没有回头了,现在它支持调试、语法自动完成等等...https://code.visualstudio.com/docs/other/unity - Isma
警告/注意事项:我发现这是一个可行的解决方案,直到我想使用“附加到进程…”方法调试我的应用程序。我正在使用Xamarin Studio 6.3,它不支持Unity调试开箱即用。 - rodamn

0
如果您正在使用多个显示器,MonoDevelop崩溃的一个原因是在上一个会话期间将IDE打开在辅助显示器中。在这种情况下,您不需要删除所有首选项,而是编辑MonoDevelopProperties.xml并删除WorkbenchMemento节点内的“bounds”属性:

 <Property key="bounds" value="-37, 162, 1920, 1020" />

0

如果您正在使用两个或更多的显示器,请尝试将Unity IDE移动到另一个显示器,然后启动MonoDevelop。 由于某种原因,如果您在不同的显示器上关闭了MonoDevelop主窗口,并尝试在另一个显示器上重新启动它,它会崩溃。


网页内容由stack overflow 提供, 点击上面的
可以查看英文原文,
原文链接