Summary: | Widget disposal causes NullPointerException | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [RT] RAP | Reporter: | Rüdiger Herrmann <ruediger.herrmann> | ||||||
Component: | RWT | Assignee: | Benjamin Muskalla <b.muskalla> | ||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P1 | ||||||||
Version: | 1.0 | ||||||||
Target Milestone: | --- | ||||||||
Hardware: | PC | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Rüdiger Herrmann
2007-07-07 06:00:04 EDT
Created attachment 73242 [details]
Stack trace
This problem occurs also in other dispose situations. It seems that "something" can cause the widget field in the lca is null but the currentWidgetRef has a value -> ensureWidgetRef() tries to set the new widget ref and fails to due to the null of the widget field. Checking widget against null in JSWriter:506 (maybe outdated) solves this problem for me. But I'm not sure if it's the cause for other problems (have much trouble at the moment on other sides - not yet sure if it's related). I think to should be definitely fixed before the M5 milestone. Will try to provide a snippet to reproduce this situation. Changes priority to P1 Created attachment 73612 [details]
example snippet
The problem is the order in which the widgets are disposed.
Fixed in CVS. |