Bug 641905 - "Default Policies" menu item causes intermittent assertion errors and crashes
Summary: "Default Policies" menu item causes intermittent assertion errors and crashes
Status: RESOLVED DUPLICATE of bug 646284
Alias: None
Product: MonoDevelop
Classification: Mono
Component: general (show other bugs)
Version: SVN
Hardware: x86-64 openSUSE 11.3
: P5 - None : Critical
Target Milestone: ---
Assignee: MD Bugs
QA Contact: MD Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-25 19:08 UTC by IB Board
Modified: 2010-10-27 09:17 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
Stack trace from crash when opening Default Policies (6.68 KB, text/x-log)
2010-09-25 19:08 UTC, IB Board
Details

Note You need to log in before you can comment on or make changes to this bug.
Description IB Board 2010-09-25 19:08:51 UTC
Created attachment 391546 [details]
Stack trace from crash when opening Default Policies

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.8 SUSE/7.0.528.0 (KHTML, like Gecko) Chrome/7.0.528.0 Safari/534.8

When trying to view the "Default Policies" dialog, MonoDevelop will sometimes crash with a failed assertion from the tree. I've added in a quick bit of logging just as it enters the method and whether it crashes or not seems to depend on what the item is that it thinks should be selected. If section label is ".NET Naming Policies" then it will crash, but if it is "Source Code" or other sections then it works fine. Sometimes opening the Preferences before the Default Policies seems to fix it, but that could just be coincidence.

Reproducible: Sometimes

Steps to Reproduce:
1. Start the latest MD
2. Edit > Default Policies
Actual Results:  
MonoDevelop sometimes crashes because of a failed assertion:

(G_NODE (iter->user_data)->parent != NULL)

Expected Results:  
Default Policies are shown
Comment 1 Lluis Sanchez 2010-10-27 09:17:02 UTC
Already fixed.

*** This bug has been marked as a duplicate of bug 646284 ***