Skip to content

Conversation

@matthiasblaesing
Copy link
Contributor

Manipulation requests of filteredNotifications are only partially covered by synchronization on notifications. Manipulations in add and delete were not protected. This might explain undefined behavior if the list is read while it is being modified.

Closes: #8956

@matthiasblaesing matthiasblaesing added this to the NB29 milestone Oct 26, 2025
@matthiasblaesing matthiasblaesing added UI User Interface ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) labels Oct 26, 2025
Copy link
Member

@mbien mbien left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changes look good. Couldn't come up with a scenario where a null element could have made it into the list though.

unfortunately the user didn't post the start of the log - the first exception might have looked differently (e.g ConcurrentModificationException).

@matthiasblaesing matthiasblaesing merged commit 18004f9 into apache:master Nov 9, 2025
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci:dev-build [ci] produce a dev-build zip artifact (7 days expiration, see link on workflow summary page) UI User Interface

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NullPointerException in org.netbeans.modules.notifications.NotificationImpl.isRead

2 participants