| Summary: | NPE when closing TS Explorer | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] Tigerstripe | Reporter: | Navid Mehregani <nmehrega> | ||||
| Component: | UI | Assignee: | Daniel Johnson <danijoh2> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | 0.5M0 | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Navid Mehregani
Dan, can you please take a look whenever you get a chance? Thanks! Created attachment 177481 [details]
patch_321140.txt
My fix is to not call a super.dispose method. Is this safe? After tracking down the instances I believe that another object was calling the dispose method of the parent class, so not calling it in the child should be ok. I really don't know the details enough to know if this is the correct solution, but it does seem to work.
Variables I watched to come to this conclusion:
JavaNavigatorContentProvider.java: fStateModel
PackageExplorerLabelProvider.java: fContentProvider
Class Changed: TigerstripeContentProvider
Thanks Dan! Sorry, but I'm a bit hesitant to apply your patch. JavaNavigatorContentProvider is an internal class that we shouldn't be sub-classing in the first place. I suspect that this will go away when bug#317761 is completed. Having the NPE there causes a bit of annoyance when debugging TS code (with an exception breakpoint enabled), but other than that, I don't think it causes any major problems on our side. I'm going to mark this defect as WONTFIX. It'll be resolved once bug#317761 is completed. |