[Mono-bugs] [Bug 467216] New: Treeview causing applications to become unresponsive

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=467216


           Summary: Treeview causing applications to become unresponsive
    Classification: Mono
           Product: Mono: Class Libraries
           Version: unspecified
          Platform: i686
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Windows.Forms
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: paul at all-the-johnsons.co.uk
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


Created an attachment (id=265908)
 --> (https://bugzilla.novell.com/attachment.cgi?id=265908)
Example code for the problem

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2)
Gecko/20090107 Fedora/3.1-0.4.beta2.fc11 Minefield/3.1b2

Using the code below and compiling using svn 123722, an application is created.

When run, a window appears with two options. If I select the expand on the
first, two things happen. First, the second list title appears at the bottom of
the window (it's been pushed down but the other child nodes are not displayed).
The application then either kills a mouse click or stops focus going to other
windows. It has to be killed by logging into a terminal, finding the PID and
manually killing.

If the second tree is clicked to expand, the application then just kills the
mouse or stops focus going to other windows.

Tested using Fedora rawhide.

Reproducible: Always

Steps to Reproduce:
1. Compile example code
2. mono treeview2.exe
3.
Actual Results:  
Something inhibits the mouse click event being seen by the X server (by the
looks of it).

Expected Results:  
The nodes should appear

I have tested this on a number of other machines (both x86 and x86_64 and they
all fail with the same problem).

-- 
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.