Difference between revisions of "Developer Meetings/20121009"
From Slicer Wiki
m (→Conclusion) |
|||
Line 19: | Line 19: | ||
** Nicole mentioned that the Brain Atlas dataset taking more than one hour to load on a linux debug build (SPL workstation) | ** Nicole mentioned that the Brain Atlas dataset taking more than one hour to load on a linux debug build (SPL workstation) | ||
** Andriy discussed the crash happening when closing slicer without "closing the scene" first after running ChangeTracker. See issue [http://www.na-mic.org/Bug/view.php?id=2590 2590] | ** Andriy discussed the crash happening when closing slicer without "closing the scene" first after running ChangeTracker. See issue [http://www.na-mic.org/Bug/view.php?id=2590 2590] | ||
+ | ** Andriy also mentioned the work done related the memory leaks associated with ChangeTracker tutorial. See [http://www.na-mic.org/Bug/view.php?id=2588 2588]. Julien pointed the Slicer wiki page listing debugging approach that could be used to "Track a crash while accessing already deleted object pointer". See http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Tutorials/Troubleshooting |
Revision as of 20:26, 9 October 2012
Home < Developer Meetings < 20121009Attendees:
To discuss
- Tutorial testing status
- ChangeTracker standing issues:
- Crash if close slicer w/o closing scene: http://www.na-mic.org/Bug/view.php?id=2590
- 1 matrix and 12 vtkCommands are leaking: http://www.na-mic.org/Bug/view.php?id=2588
- ChangeTracker standing issues:
- Discuss commit r21147
- related issue 2534
- Style and Coding Conventions discussion topics
- Commit message style. See here
- Backwards compatibility and deprecation
- Q_ASSERT vs qDebug, and vtkErrorMacro
- Memory management from 'Create' methods [1]
Conclusion
- Talked about the factory and Linux VM before every body joined
- Initiated discussion about Tutorial testing
- Nicole mentioned that the Brain Atlas dataset taking more than one hour to load on a linux debug build (SPL workstation)
- Andriy discussed the crash happening when closing slicer without "closing the scene" first after running ChangeTracker. See issue 2590
- Andriy also mentioned the work done related the memory leaks associated with ChangeTracker tutorial. See 2588. Julien pointed the Slicer wiki page listing debugging approach that could be used to "Track a crash while accessing already deleted object pointer". See http://www.slicer.org/slicerWiki/index.php/Documentation/Nightly/Developers/Tutorials/Troubleshooting