This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: |
Bytecode patch java.awt.Component to test EventQueue.isDispatchThread() |
| Product: |
platform
|
Reporter: |
_ tboudreau <tboudreau> |
| Component: |
Window System | Assignee: |
issues@platform <issues> |
| Status: |
NEW
---
|
|
|
| Severity: |
blocker
|
CC: |
saubrecht
|
| Priority: |
P3
|
|
|
| Version: |
6.x | |
|
| Hardware: |
All | |
|
| OS: |
All | |
|
|
Issue Type:
|
ENHANCEMENT
|
Exception Reporter:
|
|
|---|
A major source of deadlocks is constructing components on non-AWT threads. It would be useful if for commit-validation (or perhaps in dev builds?) we could bytecode-patch java.awt.Component with { assert EventQueue.isDispatchThread() : "Component constructed off AWT thread - can lead to deadlocks" } I just tried it and found a huge amount of components (mostly from mobility vmd module) which are created on the wrong thread.