Opened 8 years ago
Closed 8 years ago
#56 closed defect (fixed)
exception thrown when creating new breakpoint (no serious consequences)
| Reported by: | jd | Owned by: | jd |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description
This exception occurs when creating a new breakpoint using the editor. Except for cluttering up the console, this seems to have no negative consequences.
Exception in thread "AWT-EventQueue?-0" java.util.ConcurrentModificationException?
at java.util.LinkedList?$ListItr?.checkForComodification(LinkedList?.java:761) at java.util.LinkedList?$ListItr?.next(LinkedList?.java:696) at org.kahina.core.control.KahinaController?.processEvent(KahinaController?.java:67) at org.kahina.core.gui.breakpoint.BreakpointEditorWindow?.actionPerformed(BreakpointEditorWindow?.java:158) at javax.swing.AbstractButton?.fireActionPerformed(AbstractButton?.java:1995) at javax.swing.AbstractButton?$Handler.actionPerformed(AbstractButton?.java:2318) at javax.swing.DefaultButtonModel?.fireActionPerformed(DefaultButtonModel?.java:387) at javax.swing.DefaultButtonModel?.setPressed(DefaultButtonModel?.java:242) at javax.swing.plaf.basic.BasicButtonListener?.mouseReleased(BasicButtonListener?.java:236) at java.awt.Component.processMouseEvent(Component.java:6267) at javax.swing.JComponent.processMouseEvent(JComponent.java:3267) at java.awt.Component.processEvent(Component.java:6032) at java.awt.Container.processEvent(Container.java:2041) at java.awt.Component.dispatchEventImpl(Component.java:4630) at java.awt.Container.dispatchEventImpl(Container.java:2099) at java.awt.Component.dispatchEvent(Component.java:4460) at java.awt.LightweightDispatcher?.retargetMouseEvent(Container.java:4577) at java.awt.LightweightDispatcher?.processMouseEvent(Container.java:4238) at java.awt.LightweightDispatcher?.dispatchEvent(Container.java:4168) at java.awt.Container.dispatchEventImpl(Container.java:2085) at java.awt.Window.dispatchEventImpl(Window.java:2478) at java.awt.Component.dispatchEvent(Component.java:4460) at java.awt.EventQueue?.dispatchEvent(EventQueue?.java:599) at java.awt.EventDispatchThread?.pumpOneEventForFilters(EventDispatchThread?.java:269) at java.awt.EventDispatchThread?.pumpEventsForFilter(EventDispatchThread?.java:184) at java.awt.EventDispatchThread?.pumpEventsForHierarchy(EventDispatchThread?.java:174) at java.awt.EventDispatchThread?.pumpEvents(EventDispatchThread?.java:169) at java.awt.EventDispatchThread?.pumpEvents(EventDispatchThread?.java:161) at java.awt.EventDispatchThread?.run(EventDispatchThread?.java:122)
Change History (2)
comment:1 Changed 8 years ago by jd
- Priority changed from minor to major
- Status changed from new to assigned
comment:2 Changed 8 years ago by jd
- Resolution set to fixed
- Status changed from assigned to closed
Fixed. The fail-fast list traversal during event distribution in the controller caused problems when multiple threads were involved.
This happens all the time in the breakpoint editor, e.g. when selecting constraint types.
It is also for this reason that the combo box menus used for node constraint assembly tend not to close after selecting an item (the exception occurs as a result of the selection event, causing the process of closing the combo box menu to abort).
The problem obviously lies in message handling, perhaps some circularity that results from lack of care when planning the messaging system within the breakpoint editor.