Bug - Fixed Runnable in event dispatch thread

fronobulax

fronobulax

Developer
Staff member
See attached log which I just noticed from a couple of days ago. I think I did Tools->Mushroom Plot accidentally with a character who did not have a plot. I'm posting because I have a vague recollection that the "Runnable in event dispatch thread" is actually a trap added to help diagnose and fix a threading issue.
 

Attachments

Code: 
Runnable in event dispatch thread
class java.lang.Exception: Runnable in event dispatch thread
java.lang.Exception: Runnable in event dispatch thread
	at net.sourceforge.kolmafia.StaticEntity.printStackTrace(StaticEntity.java:361)
	at net.sourceforge.kolmafia.RequestThread.postRequest(RequestThread.java:219)
	at net.sourceforge.kolmafia.RequestThread.postRequest(RequestThread.java:185)
	at net.sourceforge.kolmafia.session.MushroomManager.ownsPlot(MushroomManager.java:626)
	at net.sourceforge.kolmafia.session.MushroomManager.initialize(MushroomManager.java:602)
	at net.sourceforge.kolmafia.session.MushroomManager.getMushroomManager(MushroomManager.java:174)
	at net.sourceforge.kolmafia.swingui.panel.MushroomPlotPanel.plotChanged(MushroomPlotPanel.java:223)
	at net.sourceforge.kolmafia.swingui.panel.MushroomPlotPanel.<init>(MushroomPlotPanel.java:124)
	at net.sourceforge.kolmafia.swingui.MushroomFrame.<init>(MushroomFrame.java:51)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
	at java.lang.reflect.Constructor.newInstance(Unknown Source)
	at net.sourceforge.kolmafia.CreateFrameRunnable.runConstruction(CreateFrameRunnable.java:286)
	at net.sourceforge.kolmafia.CreateFrameRunnable.createFrame(CreateFrameRunnable.java:182)
	at net.sourceforge.kolmafia.CreateFrameRunnable.run(CreateFrameRunnable.java:164)
	at java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.run(Unknown Source)
Runnable in event dispatch thread
 
Revision 13318 will load the mushroom plot in a different thread than the Swing thread.

When investigating when we tried to load the plot, I was surprised to learn that I was doing it at login because I have had a plantingScript configured for years, although I've not actually owned a mushroom plot for years. If we try to load your plot and you don't own one yet, we'll now give you an error immediately after making the request, rather than silently ignoring it - repeatedly, perhaps.
 
You must log in or register to reply here.
Back
Top