News:

Plan-G has over 1700 followers on FACEBOOK! Click HERE and add your support

Main Menu

Still struggling with the latest version

Started by FlyingAxx, March 10, 2014, 10:53:44 PM

Previous topic - Next topic

FlyingAxx

Hello Tim,

As I reported, the obviously to .NET 4.5 related problems to even boot Plan-G disappeared but it doesn't run as stable as it should (at least not for me).

1st: Connecting via Pipe does not work each time (sometime it does, sometimes not). IP4, IP6 and FSUIPC works fine. However, I observed just once a strange delay even if it should be done each second.
2nd: Plan-G crashes from time to time. The only common thing was that it happened while rolling on ground or being quite close to it after take-off or in the finals. This happens no matter what connection is chosen.

The Logfile is enclosed (it's quite long). I just changed the user name  ;).
Regards,
Axel

tim arnot

The windows crash report might shed some light on it...

Tim. @TimArnot

FlyingAxx

Tim,

Here it is (sorry partly in German). The first event was (again) .NET obviously but never again later on.


#1
:
Protokollname: Application
Quelle:        .NET Runtime
Datum:         09.03.2014 20:28:40
Ereignis-ID:   1026
Aufgabenkategorie:Keine
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      xxxxx
Beschreibung:
Anwendung: Plan-G3.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund eines Ausnahmefehlers beendet.
Ausnahmeinformationen: System.ArgumentException
Stapel:
   bei System.Array.Copy(System.Array, Int32, System.Array, Int32, Int32, Boolean)
   bei System.Collections.Generic.Queue`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].SetCapacity(Int32)
   bei System.Collections.Generic.Queue`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Enqueue(System.__Canon)
   bei BeatlesBlog.SimConnect.SimConnect+Networking.ReceiveBodyCallback(System.IAsyncResult)
   bei System.Net.LazyAsyncResult.Complete(IntPtr)
   bei System.Net.ContextAwareResult.CompleteCallback(System.Object)
   bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   bei System.Net.ContextAwareResult.Complete(IntPtr)
   bei System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr)
   bei System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   bei System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-09T19:28:40.000000000Z" />
    <EventRecordID>82713</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxxxx</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Anwendung: Plan-G3.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund eines Ausnahmefehlers beendet.
Ausnahmeinformationen: System.ArgumentException
Stapel:
   bei System.Array.Copy(System.Array, Int32, System.Array, Int32, Int32, Boolean)
   bei System.Collections.Generic.Queue`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].SetCapacity(Int32)
   bei System.Collections.Generic.Queue`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Enqueue(System.__Canon)
   bei BeatlesBlog.SimConnect.SimConnect+Networking.ReceiveBodyCallback(System.IAsyncResult)
   bei System.Net.LazyAsyncResult.Complete(IntPtr)
   bei System.Net.ContextAwareResult.CompleteCallback(System.Object)
   bei System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   bei System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   bei System.Net.ContextAwareResult.Complete(IntPtr)
   bei System.Net.LazyAsyncResult.ProtectedInvokeCallback(System.Object, IntPtr)
   bei System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
   bei System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
</Data>
  </EventData>
</Event>


#2
:
Protokollname: Application
Quelle:        Application Error
Datum:         09.03.2014 20:28:40
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      xxxxx
Beschreibung:
Name der fehlerhaften Anwendung: Plan-G3.exe, Version: 3.1.0.82, Zeitstempel: 0x53109070
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 6.1.7601.18229, Zeitstempel: 0x51fb1116
Ausnahmecode: 0xe0434352
Fehleroffset: 0x0000c41f
ID des fehlerhaften Prozesses: 0x1210
Startzeit der fehlerhaften Anwendung: 0x01cf3bc900d94d0d
Pfad der fehlerhaften Anwendung: D:\Flightsims\Navigation\Plan-G v3.1\Plan-G3.exe
Pfad des fehlerhaften Moduls: C:\Windows\syswow64\KERNELBASE.dll
Berichtskennung: 0474bb8f-a7c1-11e3-81a1-14dae94c6f2c
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-09T19:28:40.000000000Z" />
    <EventRecordID>82714</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxxxx</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Plan-G3.exe</Data>
    <Data>3.1.0.82</Data>
    <Data>53109070</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.18229</Data>
    <Data>51fb1116</Data>
    <Data>e0434352</Data>
    <Data>0000c41f</Data>
    <Data>1210</Data>
    <Data>01cf3bc900d94d0d</Data>
    <Data>D:\Flightsims\Navigation\Plan-G v3.1\Plan-G3.exe</Data>
    <Data>C:\Windows\syswow64\KERNELBASE.dll</Data>
    <Data>0474bb8f-a7c1-11e3-81a1-14dae94c6f2c</Data>
  </EventData>
</Event>



#3
(and the following one):
Protokollname: Application
Quelle:        Application Error
Datum:         09.03.2014 21:51:54
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:     xxxxx
Beschreibung:
Name der fehlerhaften Anwendung: Plan-G3.exe, Version: 3.1.0.82, Zeitstempel: 0x53109070
Name des fehlerhaften Moduls: ntdll.dll, Version: 6.1.7601.18247, Zeitstempel: 0x521ea8e7
Ausnahmecode: 0xc0000374
Fehleroffset: 0x000ce753
ID des fehlerhaften Prozesses: 0x1580
Startzeit der fehlerhaften Anwendung: 0x01cf3bd1ce2a8c6d
Pfad der fehlerhaften Anwendung: D:\Flightsims\Navigation\Plan-G v3.1\Plan-G3.exe
Pfad des fehlerhaften Moduls: C:\Windows\SysWOW64\ntdll.dll
Berichtskennung: a4d72c0f-a7cc-11e3-81a1-14dae94c6f2c
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-03-09T20:51:54.000000000Z" />
    <EventRecordID>82719</EventRecordID>
    <Channel>Application</Channel>
    <Computer>xxxxx</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Plan-G3.exe</Data>
    <Data>3.1.0.82</Data>
    <Data>53109070</Data>
    <Data>ntdll.dll</Data>
    <Data>6.1.7601.18247</Data>
    <Data>521ea8e7</Data>
    <Data>c0000374</Data>
    <Data>000ce753</Data>
    <Data>1580</Data>
    <Data>01cf3bd1ce2a8c6d</Data>
    <Data>D:\Flightsims\Navigation\Plan-G v3.1\Plan-G3.exe</Data>
    <Data>C:\Windows\SysWOW64\ntdll.dll</Data>
    <Data>a4d72c0f-a7cc-11e3-81a1-14dae94c6f2c</Data>
  </EventData>
</Event>


Hope you can see something.
Regards,
Axel

tim arnot

The first one is Simconnect. That's been a known issue since forever, and there's nothing I can do since it's a 3rd party module with no source. The other two I have no idea - there's no stack trace, no information other than the name of the program and the dll. Best I can say is something crashed doing something.

Tim. @TimArnot

FlyingAxx

Quote from: tim arnot on March 12, 2014, 09:06:17 AM
The first one is Simconnect. That's been a known issue since forever, and there's nothing I can do since it's a 3rd party module with no source. The other two I have no idea - there's no stack trace, no information other than the name of the program and the dll. Best I can say is something crashed doing something.

Cool answer  >:D   :P

I have to see if it happens in the future, too. At least there had been no real recognizable pattern. Thanks for your efforts nonetheless.
Regards,
Axel

FlyingAxx

Quote from: tim arnot on March 12, 2014, 09:06:17 AM
The first one is Simconnect. That's been a known issue since forever, and there's nothing I can do since it's a 3rd party module with no source. The other two I have no idea - there's no stack trace, no information other than the name of the program and the dll. Best I can say is something crashed doing something.

Hi Tim,

Today nothing happened at all. Same environment, nothing changed, and an absolute stable Plan-G (regarding crashes).   8)
I have no idea what happened last Sunday.

However, there is one remaining issue. After pausing a flight while being connected you have to disconnect and connect again in order to get you flight path updated. Otherwise the plain keeps sitting and waiting for the Nowhere Man. This seems even to happen when an other guy (I use to fly in a small group via FsHost) does the same. His plane did not update until going to the above procedure. Is this again a known issue of SimConnect? I don't have such behaviour when tracking with FS Commander.
Regards,
Axel

tim arnot

I was not aware of that issue, I'll have to look into it. Is it only when you are running multiplayer?

Tim. @TimArnot

FlyingAxx

Quote from: tim arnot on March 17, 2014, 02:01:13 AM
I was not aware of that issue, I'll have to look into it. Is it only when you are running multiplayer?

Yes, it happens in multiplayer mode. I just did some more tests and it neither happened when just flying for myself nor when I'm alone on the server in multiplayer mode. I think I will make some tests again next Sunday (sorry, no chance before).
Regards,
Axel