[Mono-bugs] [Bug 612635] New: Delegate Invocation hangs WebBrowser
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Tue Jun 8 14:53:21 EDT 2010
http://bugzilla.novell.com/show_bug.cgi?id=612635
http://bugzilla.novell.com/show_bug.cgi?id=612635#c0
Summary: Delegate Invocation hangs WebBrowser
Classification: Mono
Product: Mono: Class Libraries
Version: 2.4.x
Platform: i686
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Windows.Forms
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: andy at gohanman.com
QAContact: mono-bugs at lists.ximian.com
Found By: Other
Blocker: No
Created an attachment (id=367909)
--> (http://bugzilla.novell.com/attachment.cgi?id=367909)
Sample code
Description of Problem:
A delegate invocation inside WebBrowser.WebBrowserDocumentCompletedEventHandler
produces inconsistent results. More often than not result is program appears to
be stuck.
Steps to reproduce the problem:
1. Compile the attached test.cs
2. Run result
Actual Results:
Varies. Generally prints "start" then hangs indefinitely. If the URL being
loaded contains content, no rendering takes place.
Expected Results:
Print "start" and "stop", render URL.
How often does this happen?
If the URL being loaded is extremely simple - a text file containing just
opening and closing html tags, for instance - the program will *occasionally*
print both "start" and "stop". Roughly 10% of the time in my experience. For
any non-trivial URL, the only result I've seen is the indefinite hang.
Additional Information:
OS: Fedora 12
Mono v. 2.4.3
gluezilla v. 2.6
Compiled by: gmcs -target:exe -r:System.Drawing -r:System.Windows.Forms
-out:test.exe test.cs
Removing the delegate invocation fixes the problem for every URL I've tried. I
realize the delegate call is unnecessary in the provided code. I encountered
this problem trying to write a simplified test case for a different bug.
--
Configure bugmail: http://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