| Summary: | [Widgets] crash in AbstractTreeViewer.updateChildren, Tree.destroyItem | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | David Green <greensopinion> | ||||||||
| Component: | SWT | Assignee: | Platform-SWT-Inbox <platform-swt-inbox> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | robert.elves | ||||||||
| Version: | 3.5 | Keywords: | triaged | ||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | Macintosh | ||||||||||
| OS: | Mac OS X | ||||||||||
| Whiteboard: | stalebug | ||||||||||
| Attachments: |
|
||||||||||
|
Description
David Green
Created attachment 148027 [details]
full crash report
I was able to reproduce this one today using Version: 3.6.0 Build id: I20091027-0100 The actions I took that caused the problem: # deleted folder with 1000's of files in it from the filesystem # refreshed the folder in the package explorer that represented the deleted folder Created attachment 151739 [details]
new crash report
Created attachment 162204 [details]
crash report
Crashed again for me today.
Eclipse SDK
Version: 3.6.0
Build id: N20100305-2003
This latest crash occurred immediately after doing a *Replace With -> Base Revision* in the Package Explorer view with Subclipse. Bug triaged, visit https://wiki.eclipse.org/SWT/Devel/Triage for more information. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. *** Bug 274349 has been marked as a duplicate of this bug. *** |