Bug 14266 - Crashing when loading solutions
Summary: Crashing when loading solutions
Status: RESOLVED DUPLICATE of bug 14211
Alias: None
Product: Runtime
Classification: Mono
Component: JIT ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- major
Target Milestone: ---
Assignee: Bugzilla
URL:
: 14280 ()
Depends on:
Blocks:
 
Reported: 2013-08-27 07:06 UTC by Mike James
Modified: 2013-08-29 21:19 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Crash log from customer (66.36 KB, application/octet-stream)
2013-08-27 07:06 UTC, Mike James
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED DUPLICATE of bug 14211

Description Mike James 2013-08-27 07:06:41 UTC
Created attachment 4721 [details]
Crash log from customer

A number of customers have reported that after updating to Xamarin Studio Version: 4.0.12.3, they are no longer able to load in solutions. 

Crash log attached.
Comment 1 Mikayla Hutchinson [MSFT] 2013-08-27 13:09:55 UTC
JIT crash:

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x9268fa6a __pthread_kill + 10
1 libsystem_c.dylib 0x919e2b2f pthread_kill + 101
2 libsystem_c.dylib 0x91a194ec abort + 168
3 libmonosgen-2.0.dylib 0x010a7980 mono_handle_native_sigsegv +
592
4 libmonosgen-2.0.dylib 0x010fd01d sigabrt_signal_handler + 109
5 libsystem_c.dylib 0x919cd8cb _sigtramp + 43
6 ??? 0xffffffff 0 + 4294967295
7 libmonosgen-2.0.dylib 0x010fcfb0 sigusr1_signal_handler + 272
8 libsystem_c.dylib 0x91a194ec abort + 168
9 libmonosgen-2.0.dylib 0x0124ed9c monoeg_g_logv + 188
10 libmonosgen-2.0.dylib 0x0124edcb monoeg_assertion_message + 43
11 libmonosgen-2.0.dylib 0x0105e158 inline_method + 2088
12 libmonosgen-2.0.dylib 0x01039e79 mono_method_to_ir + 76777
13 libmonosgen-2.0.dylib 0x0100af78 mini_method_compile + 5768
14 libmonosgen-2.0.dylib 0x0100ca8a
mono_jit_compile_method_with_opt + 1610
15 libmonosgen-2.0.dylib 0x0100d4c9 mono_jit_compile_method + 41
16 libmonosgen-2.0.dylib 0x010ac952 common_call_trampoline + 1042
17 libmonosgen-2.0.dylib 0x010aa3fa mono_vcall_trampoline + 202
Comment 2 Mikayla Hutchinson [MSFT] 2013-08-27 13:10:25 UTC
Need IDE logs to see the failed assertion message.
Comment 3 Mikayla Hutchinson [MSFT] 2013-08-27 13:55:58 UTC
*** Bug 14280 has been marked as a duplicate of this bug. ***
Comment 4 Zoltan Varga 2013-08-29 21:15:00 UTC
How can I reproduce this ?
Comment 5 Zoltan Varga 2013-08-29 21:19:16 UTC

*** This bug has been marked as a duplicate of bug 14211 ***