bukkitgui2
bukkitgui2 copied to clipboard
Bertware
BukkitGUI2 stops responding on plugin update
Whenever I attempt to install a selected update for a plugins, bukkitgui stops working and says windows is trying to fix the problem. Files that help describe the problem (Straight from windows 7 error): C:\Users******\AppData\Local\Temp\WERC7A6.tmp.WERInternalMetadata.xml C:\Users******\AppData\Local\Temp\WERE3AF.tmp.mdmp
Can you get the GUI logfile from %appdata%/Bertware/bukkitgui2/log ? (get it straight after it crashed)
Some more info about the problem, it only happens when the server is running.
Here's the log: http://pastebin.com/P8J058Dg
It doesn't seem to indicate a sign of a struggle.
Does this happen for any plugin, anytime? or only select plugins, or when the server is running? I assume you're using the update dialog (which allows to update multiple plugins) to update them.
I am using plugin update dialog, and the problem happened with HolographicDisplays, GriefPrevention, and Vault until I tried it with the server stopped, only ever worked with worldguard with the server still running.
This same problem occurs when I attempt to download the latest development build for spigot
Just tried downloading spigot dev build with build 248, works for me without crashing (though the download box dissapears all of a sudden, probably the file can't be downloaded). I'll look at the cause of the failing download, but the crashes would make me think it's something with your .NET installation? (It's just a guess, but any issue in the GUI should show a "Unexpected error" dialog box with debug information, if it doesn't it's likely to be .NET related)
After a reinstall of .net framework, the development build download issue no longer persists, but the plugin update issue does.
Some more info on the problem, I have Essentials vTeamCity and when I "Update it", it actually just downloads the latest regular copy of essentials (v2.13.1), without deleting the vTeamCity version. This plugin update does not trigger the not responding window. Updating GreifPrevention from v10.1 to 10.5.6, the issue does occur. This error might be caused by the programs unwillingness to delete the previous version.
Hmmm, it doesn't delete the previous version because it should "overwrite" the previous version, keeping the name. However, looks like they're linked in the wrong way though. I'll improve the plugin downloading and naming scheme though, so the rewrite issue gets fixed
Commits 94df625790dfbf17161d0f75cede0963013c42e2 118905b3cff6d62a4d46603c6226f48bdbeb5794 might affect this issue, parts of the plugin updater have been optimzed and cleaned. Though the optimizations were not directly related to this ticked, they might have had a positive effect.
Do these optimizations include stopping the server before updating plugin? I believe that unless you have another plugin (The one used to check and modify players inventory perhaps) disconnecting that plugin from the server, you'll have to stop the server before updating.
The optimizations improve code etc, but don't change the behaviour. The server doesn't need to be stopped to update plugins. While plugins can't be removed while the server is running, they can be overwritten, so you only have to reload to apply the changes. (Even while reload is discouraged and full server restarts are better, this makes updating easier)
So, a little bit more info on the current situation: The "stopped working" windows error has not been resolved, however, you can still interact with BukkitGUI despite the error. The "Downloading" dialog does not automatically close on completion, so after closing it, the plugin update window displays a dialog that says that the plugin has been installed and you can restart your server to enable it. This installation method has only ever worked with one plugin (ClearLagg) so far. The windows error never goes away, but BukkitGUI works exactly like it did without the error.
I'll try to reproduce it again. The problem itself is quite odd, since Windows is saying it crashed while it's still working. (it's possible for the GUI to detect errors and keep working, but once Windows gives an error, or the program crashes, normal behaviour would be to stop working altogether )
Do keep in mind that the update of the plugin does not complete successfully. My guess is that the thread it's working on causes the error, but the threads for the main GUI continue to work.
I'm note certain. But I'm getting a similar error at startup of the bukkitgui2. It started after a java crash.
It's not directly related to the updating of plugins (I think). But the error is what technoguy20000 describes. The "the program stopped working" shows up, but the gui and the server actually works just fine.
It happens at every startup.
