You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is probably because the bootloader process does not happen in a separate thread. There is an attempt to do this by using SwingUtilities.invokeLater, but that doesn't spawn a new thread, it just runs the given function later in the event dispatching thread, which still locks up the GUI thread for as long as the function runs.
The proper fix this is to use an actual thread, but this should probably be combined by integrating the burn bootloader process into the verify/upload process (which should be simplified a lot - there's a lot of (unneeded) processing abstractions in there).
The text was updated successfully, but these errors were encountered:
Nope, and I can't commit the time needed to dive into this now. Also, I'm not sure if the recent GUI refactor PR changed this, it's certainly something that is in the same area and needs to be resolved by refactoring...
I can reproduce this with Arduino IDE 1.5.6-r2 (the latest IDE version at the time of the report) on Windows but it does not occur for me with Arduino IDE 1.8.3 so I'm going to close this.
If the issue still occurs for anyone with the latest IDE version please comment and I'll reopen.
Tested using the ide-1.5.x branch from git.
This is probably because the bootloader process does not happen in a separate thread. There is an attempt to do this by using
SwingUtilities.invokeLater
, but that doesn't spawn a new thread, it just runs the given function later in the event dispatching thread, which still locks up the GUI thread for as long as the function runs.The proper fix this is to use an actual thread, but this should probably be combined by integrating the burn bootloader process into the verify/upload process (which should be simplified a lot - there's a lot of (unneeded) processing abstractions in there).
The text was updated successfully, but these errors were encountered: