Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

Bug Report - Crash on bad data in ATIS Freq Field


Mike Burke 1145825
 Share

Recommended Posts

Mike Burke 1145825
Posted
Posted

Not sure if there's an approved channel for bug reports - I thought I had seen a github or something earlier but can't track down the URL. If so, direct me there and I can open one up.

 

Entering something goofy like text in ATIS Frequency box causes a crash (blame my inner QA tester).

 

Link to comment
Share on other sites

Justin Shannon
Posted
Posted

I could have sworn I added a validation check for that...I'll have that fixed in the next update.

 

Thanks for the report.

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Ray Lang
Posted
Posted

Justin i get the same problem where i get a crash in the atis field. Using the latest update of vAtis.

For Wellington Airport (NZWN) the atis freq 126.900 vAtis reports sometimes a invalid freq.

 

  • ==============================================================================
    vATIS, Version=1.0.7152.33043, Culture=neutral, PublicKeyToken=null
    ------------------------------------------------------------------------------
    Application Information
    ------------------------------------------------------------------------------
    Program : C:\Users\Ray\AppData\Roaming\vATIS\vATIS.exe
    Time : 21/08/2014 16:54:01
    OS : Microsoft Windows NT 6.1.7601 Service Pack 1
    Culture : en-NZ
    Processors : 4
    Working Set : 46972928
    Framework : 2.0.50727.5483
    Run Time : 00:00:30.3873587
    ------------------------------------------------------------------------------
    Exception Information
    ------------------------------------------------------------------------------
    Source : System.Windows.Forms
    Method : ShowDialog
    Type : System.InvalidOperationException
    Error : Form that is already visible cannot be displayed as a modal dialog box. Set the form's visible property to false before calling showDialog.
    Stack Trace : at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
    at System.Windows.Forms.Form.ShowDialog()
    at (Object )
    at A.VSB.A(Object A)
    at A.QF.C(Boolean A, Boolean B)
    at A.QF.Q(Object A, EventArgs B)
    at System.Windows.Forms.Control.OnLostFocus(EventArgs e)
    at System.Windows.Forms.Control.WmKillFocus(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.TextBoxBase.WndProc(Message& m)
    at System.Windows.Forms.TextBox.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    ------------------------------------------------------------------------------
    2014-08-21_16.54.01.txt
    ==============================================================================

Ray Lang

Vatsim Senior Supervisor

Pacific Oceanic Partnership Admin

Have a question? Email [email protected]

spacer.png

Link to comment
Share on other sites

Justin Shannon
Posted
Posted

Ray,

 

I wasn't able to reproduce your error; however, I did make a small change to the validation code, so that may fix the issue. Once I can track down the other crash bug, I'll post an update release.

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

 Share