-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ViewerRow NPE in ViewerCell.getStyleRanges #177
Comments
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Sep 1, 2023
Do not reuse ViewerCell instance - that only caused trouble and was clearly forbidden by org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerCell). Instead let the GC do his job. Declaring the constants final formally requires API change. But it was never intended that the constants could be changed. eclipse-platform#177
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Sep 1, 2023
Do not reuse ViewerCell instance - that only caused trouble and was clearly forbidden by org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerCell). Instead let the GC do his job. Declaring the constants final formally requires API change. But it was never intended that the constants could be changed. eclipse-platform#177
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Sep 8, 2023
Do not reuse ViewerCell instance - that only caused trouble and was clearly forbidden by org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerCell). Instead let the GC do his job. Declaring the constants final formally requires API change. But it was never intended that the constants could be changed. eclipse-platform#177
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Sep 8, 2023
Do not reuse ViewerCell instance - that only caused trouble and was clearly forbidden by org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerCell). Instead let the GC do his job. Declaring the constants final formally requires API change. But it was never intended that the constants could be changed. eclipse-platform#177
jukzi
pushed a commit
to jukzi/eclipse.platform.ui
that referenced
this issue
Sep 8, 2023
Do not reuse ViewerCell instance - that only caused trouble and was clearly forbidden by org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerCell). Instead let the GC do his job. Declaring the constants final formally requires API change. But it was never intended that the constants could be changed. eclipse-platform#177
jukzi
pushed a commit
that referenced
this issue
Sep 8, 2023
Do not reuse ViewerCell instance - that only caused trouble and was clearly forbidden by org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerCell). Instead let the GC do his job. Declaring the constants final formally requires API change. But it was never intended that the constants could be changed. #177
Looks like this covered by #1078 and can be closed? |
@elsazac thanks for the hint. lets hope its fixed. just reopen if not. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
happend together with eclipse-pde/eclipse.pde#190
i don't know where that null value can come from.
My first thought was ViewerCell constructor should eager validate null argument to get to the root reason, but ColumnViewer.java:57 explicitly uses null as argument.
The text was updated successfully, but these errors were encountered: