Bug 380707

Summary: Crash on close after editing data.frame
Product: [Applications] rkward Reporter: Thomas Friedrichsmeier <thomas.friedrichsmeier>
Component: generalAssignee: RKWard Team <rkward-devel>
Status: RESOLVED NOT A BUG    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: All   
Latest Commit: Version Fixed In:
Attachments: Valgrind output when the crash is triggered
Output at --debug-level 5; The last four trace lines are likely not related (secondary thread)

Description Thomas Friedrichsmeier 2009-05-06 08:38:54 UTC 
-- This ticket was imported from http://sourceforge.net/p/rkward/bugs/45 on 2017-05-30 15:26:40 +0100 --
RKWard crashed on close under certain circumstances. Instructions to reproduce \(see this mail by manchito: https://sourceforge.net/mailarchive/forum.php?thread\_name=49FA1AD5.1010507%40gmail.com&forum\_name=rkward-devel\):

1\. Start with an empty worspace.
2\. Create a new empty dataset with default name.
3\. Try to edit the "Type" row of any variable \(double-click, then click 
again to diselect the text NOT THE CELL\).
4\. Hit the window "Close" button.
5\. Crash... \(at least for me\).

The crash seems to occur at the time when the RKEditorDataFramePart is being destroyed. I'm \*guessing\* at a double deletion problem with the part and the widget \(i.e. RKEditorDataFrame\) both trying to delete the other.
Comment 1 Thomas Friedrichsmeier 2009-05-06 08:38:54 UTC 
Valgrind output when the crash is triggered
-- Created an attachment --
Comment 2 Thomas Friedrichsmeier 2009-05-06 08:41:53 UTC 
Output at --debug-level 5; The last four trace lines are likely not related (secondary thread)
-- Created an attachment --
Comment 3 Thomas Friedrichsmeier 2017-06-04 13:33:01 UTC 
Haven't seen this in a long time, and should it still be relevant, the attached debug information is almost certainly no longer useful due to a bunch of changes in between. Closing,