[MonoDevelop] [MonoTouch] My MD freezes while debugging on Simulator

Guido Van Hoecke guivho at gmail.com
Tue Aug 7 16:20:36 UTC 2012


On 7 August 2012 15:27, Rolf Bjarne Kvinge <rolf at xamarin.com> wrote:
> Hi,
>
> It looks like MonoDevelop is stuck / very busy printing out logging
> information for a (recurring) gtk warning.
>
> I suggest you file a bug for MonoDevelop (http://bugzilla.xamarin.com) with
> the log file you provided.

https://bugzilla.xamarin.com/show_bug.cgi?id=6450

With kind regards,

Guido

>
> Rolf
>
> On Mon, Aug 6, 2012 at 9:48 PM, Guido Van Hoecke <guivho at gmail.com> wrote:
>>
>> On 6 August 2012 19:20, Rolf Bjarne Kvinge <rolf at xamarin.com> wrote:
>> > Hi,
>> >
>> > This is more for the monodevelop list, but in any case: when this
>> > happens,
>> > can you "kill -QUIT pid" the app first, then send the log file (should
>> > be
>>
>> Neither the app nor MonoDevelop obey kill -QUIT
>>
>> I attach the log file. Here's what I've done:
>>
>> - just start fresh MonoDevelop
>> - start debugging on the simulator
>> - don't interact with either MooDevelop nor with Simulator
>> - just wait couple of minutes
>> - select MonoDevelop window to detect spinning rainbow ball
>> - kill -QUIT the app process
>> - kill -QUIT the MD process
>> - The zipped log is available from
>>   https://www.dropbox.com/s/bi6we880ir6gbne/MonoDevelop.log.zip
>>
>> Please do tell me if other stuff is needed to help pinpointing this
>> problem, anything to solve this...
>>
>>
>> > ~/Library/Logs/MonoDevelop-3.0/MonoDevelop.log - but it might be
>> > different
>> > if you're using a different MonoDevelop version or if you're running
>> > multiple MonoDevelop instances at the same time).
>> >
>> > Rolf
>> >
>> > On Mon, Aug 6, 2012 at 9:07 AM, Guido Van Hoecke <guivho at gmail.com>
>> > wrote:
>> >>
>> >> When debugging on the simulator, my MD usually freezes after a varying
>> >> period of inactivity. I want it to just keep running to catch any
>> >> crashes, but it just freezes.
>> >>
>> >> The recipe is simple. I just start debugging the app, don't do
>> >> anything on the keyboard or wit the mouse, and after a while (seconds,
>> >> minutes...) MD and the Simulator are just frozen: the little rainbow
>> >> wheel keeps spinning ...
>> >>
>> >> I have to kill the MD process (kill -KILL pid) to recover.
>> >>
>> >> This may wel be caused by the app, still it is very annoying. It has as
>> >> side effect that I seldom run in debug mode, and usually do my
>> >> debugging
>> >> bmo console otput at strategic places.
>> >>
>> >> Any suggestions about how to tackle this?
>> >>
>> >> Version informationn follows (allthough this is not a recent problem:
>> >> it
>> >> has plagued me for as long as I can remember)
>> >>
>> >> MonoDevelop 3.0.3.5
>> >> Installation UUID: 7981a2f1-e51d-4ee9-941a-f90b2222409b
>> >> Runtime:
>> >>         Mono 2.10.9 (tarball)
>> >>         GTK 2.24.10
>> >>         GTK# (2.12.0.0)
>> >>         Package version: 210090011
>> >> Apple Developer Tools:
>> >>          Xcode 4.3.3 (1178)
>> >>          Build 4E3002
>> >> Monotouch: 5.2.12
>> >> Mono for Android: 4.2.4.167234518 (Evaluation)
>> >> Android SDK not found.
>> >> Build information:
>> >>         Release ID: 30003005
>> >>         Git revision: 3d53e1366933298a3fe0cdc6d0f7d00c9916564c-dirty
>> >>         Build date: 2012-07-27 19:06:34+0000
>> >>         Xamarin addins: 73ecde7c48d943adb6e33d511d3cf0661d006801
>> >> Operating System:
>> >>         Mac OS X 10.7.4
>> >>         Darwin zac.local 11.4.0 Darwin Kernel Version 11.4.0
>> >>             Mon Apr  9 19:32:15 PDT 2012
>> >>             root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64
>>
>>
>> Guido
>>
>> --
>> When the blind lead the blind they will both fall over the cliff.
>>                 -- Chinese proverb
>>
>> http://vanhoecke.org ... and go2 places!
>
>


More information about the Monodevelop-list mailing list