Praxeswow / wowclsp

Automatically exported from code.google.com/p/wowclsp
0 stars 0 forks source link

Exception on parsing #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. My combatlog is 2.7gb (I know, I know... totally spaced over the entire 
summer... That's exactly why I NEED this parser! :-)
2. I load it, and click Parse
3. Get an exception, pasted below. 

What is the expected output? What do you see instead?

************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '-1467859400' is not valid 
for 'Maximum'. 'Maximum' must be greater than or equal to 0.
Parameter name: Maximum
   at System.Windows.Forms.ProgressBar.set_Maximum(Int32 value)
   at WoW_Combatlog_Splitter.WoWCombatlogSplitter.btn_parse_Click(Object 
sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons 
button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(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)

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
    CodeBase: 
file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
WoW Combatlog Splitter
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Public/Games/World%20of%
20Warcraft/Interface/AddOns/WoWCLSP_v1.5/WoW%20Combatlog%20Splitter.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
    CodeBase: 
file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c56
1934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
    CodeBase: 
file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/Syste
m.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.4918 (NetFXspW7.050727-4900)
    CodeBase: 
file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a
3a/System.Drawing.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

What version of the product are you using? On what operating system?
Win 7 RC, with v1.5

Original issue reported on code.google.com by kclem...@gmail.com on 23 Sep 2009 at 4:15

GoogleCodeExporter commented 9 years ago
same here... got a 3.6gb combatlog... 

System.ArgumentOutOfRangeException: Value of '-645667023' is not valid for 
'Maximum'.
'Maximum' must be greater than or equal to 0.
Parameter name: Maximum

Original comment by anpr...@gmail.com on 8 Dec 2009 at 12:15

GoogleCodeExporter commented 9 years ago
i think the problem can be found in line 100, Form1.cs:
>> prg_parse.Maximum = (int)fs_olog.Length;

this line sets the maximum value for the progress bar to the file size of the 
log
file... any value above 2.147.483.647 (aka 2gb) will cause the app to crash.

Original comment by anpr...@gmail.com on 8 Dec 2009 at 12:32

GoogleCodeExporter commented 9 years ago
last night, i did need this badly, so i downloaded SharpDevelop, and changed 
the 
Form1.cs:

line 100: prg_parse.Maximum = (int) (fs_olog.Length / 1024);
line 200: prg_parse.Value = (int) (sr_olog.BaseStream.Position / 1024);

so that now, the progress bar uses kilobytes instead of bytes... this should 
give us 
headroom till the 2TB mark :)

To get it compiled, i also had to change SignManifests in the .csproj file to 
false... but i guess this is due to some limitation in SharpDevelop. 

Original comment by anpr...@gmail.com on 14 Dec 2009 at 9:34

Attachments:

GoogleCodeExporter commented 9 years ago
Same issue here. Over 2gb log file :/

Original comment by dekim...@gmail.com on 28 Jan 2011 at 1:56

GoogleCodeExporter commented 9 years ago
Well the problem occurs because the max value of the progressbar isn't set 
Correctly!

Original comment by gehannf on 4 Oct 2012 at 9:21