A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit the original URL.
The file type is application/pdf
.
Finding errors in multithreaded GUI applications
2012
Proceedings of the 2012 International Symposium on Software Testing and Analysis - ISSTA 2012
To keep a Graphical User Interface (GUI) responsive and active, a GUI application often has a main UI thread (or event dispatching thread) and spawns separate threads to handle lengthy operations in the background, such as expensive computation, I/O tasks, and network requests. Many GUI frameworks require all GUI objects to be accessed exclusively by the UI thread. If a GUI object is accessed from a non-UI thread, an invalid thread access error occurs and the whole application may abort. This
doi:10.1145/2338965.2336782
dblp:conf/issta/ZhangLE12
fatcat:n2yy2jjnkvexdbps5emvu4o4ea