[Mono-bugs] [Bug 643366] New: [Regression?] Scrollbar: "LargeChange" System.ArgumentOutOfRangeException

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sat Oct 2 17:35:06 EDT 2010



           Summary: [Regression?] Scrollbar: "LargeChange"
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.8.x
          Platform: x86-64
        OS/Version: Windows
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Windows.Forms
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: htl10 at users.sourceforge.net
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

User-Agent:       Mozilla/5.0 (X11; U; Linux; en-GB) AppleWebKit/532.4 (KHTML,
like Gecko) konqueror/4.4.5 Safari/532.4

EXCEPTION handling: System.ArgumentOutOfRangeException: Value '-15' must be
greater than or equal to 0.
Parameter name: LargeChange

this appear to be thrown by Line 453:

I have an application (unfortunately proprietary) which worked well for 2.6.x
but seem to have acquired a problem lately with the 2.8 previews. During the
course of this application running, the exception above are thrown every couple
of minutes. If the user simply acknowledge the exception and click "don't
report to microsoft", the application continues to run, apparently quite
happily. So the exception being thrown seems harmless but disruptive to the
application's operation.

Unfortunately the application itself seems to trap the exception and there is
no stack trace about which part of mono's System.Windows.Forms is calling
scrollbar and resulted in the above exception. I tried "mono
--trace=System.Windows.Forms" and the application then won't run and dies with:

 ENTER: System.Windows.Forms.Form:GetAutoScaleSize
(System.Drawing.Font)(VALUERET:02351400, Stacktrace:
abnormal program termination

Reproducible: Always

Is there any reason why Mono's Windows.System.Form should throw such an
exception? Rather than emitting a warning or some sort, resetting the
"LargeChange" value to zero, and carry on? It is the "throw an exception" part
which is disrupting the application.

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list