Please first see:

http://osbot.org/forum/topic/88656-2425-errors-starting-up-scripts/

 

I have had a few people point out this error and I get it every now and again myself.

https://gyazo.com/f3bca263fabd23d059a89d34e64866bd

 

Not script specific.
 

 

Can you post the stacktrace along with the specific OSBot version that produced the stacktrace?

A stacktrace without the OSBot version is a lot less useful.

 

The error posted by Czar was resolved in .25

1. OSBot Version (do NOT put "current version", be specific)

2. A description of the issue. Include relevant logs.

3. Are you receiving any errors in the client canvas or the logger? 

4. How can you replicate the issue?

5. Has this issue persisted through multiple versions? If so, how far back?

 

1. OSBot version: 2.4.25
2. When a script is started, either locally or from the sdn, there is an error in the script onStart(). The script terminates after completing the onExit() (I know this because I log the exit using [log("Thank you for using ShinyFighter);] in the onExit()). After terminating, according to the logger, the script is apparently started. The paint loads on the screen and closes immediately after. The GUI loads and closes immediately after. The GUI loads so I think the issue may be in how I am waiting for GUI completion because I have loggers in the onStart() that come after the GUI completion that do not get reached. I have included the code I use in the onStart() for any GUI's I use in a spoiler below.
3. See logger in spoiler below.
4. Continuously start and stop a script and it should eventually happen.
5. No, not that I know of.

Logger:

[DEBUG][12/28 11:09:20 AM]: OSBot is now ready!
[iNFO][12/28 11:09:22 AM]: Loaded 6 RS accounts!
[iNFO][12/28 11:09:22 AM]: Welcome to OSBot 2.4.25!
[iNFO][12/28 11:10:16 AM]: Updated injection hooks for client revision : 103!
[DEBUG][bot #1][12/28 11:10:16 AM]: Initializing stealth injection bot...
[iNFO][bot #1][12/28 11:10:17 AM]: Downloading latest RS2 old-school client parameters...
[DEBUG][bot #1][12/28 11:10:18 AM]: Injected bot reference into client!
[DEBUG][bot #1][12/28 11:10:18 AM]: Injected world accessors!
[DEBUG][bot #1][12/28 11:10:18 AM]: Injected 31 class and 306 field accessors!
[DEBUG][bot #1][12/28 11:10:18 AM]: Injected canvas!
[DEBUG][bot #1][12/28 11:10:18 AM]: Injected 4 model update calls!
[DEBUG][bot #1][12/28 11:10:18 AM]: Injected 12 definition calls!
[DEBUG][bot #1][12/28 11:10:18 AM]: Injected 18 definition transformation calls!
[DEBUG][bot #1][12/28 11:10:18 AM]: Injected random.dat patch for bot #1
[DEBUG][bot #1][12/28 11:10:19 AM]: Injected 2 tooltip callbacks!
[DEBUG][bot #1][12/28 11:10:19 AM]: Injected 3 config callbacks!
[DEBUG][bot #1][12/28 11:10:19 AM]: Injected 12 head message callbacks!
[DEBUG][bot #1][12/28 11:10:19 AM]: Injected 2 chatbox message callbacks!
[DEBUG][bot #1][12/28 11:10:20 AM]: Injected 29 draw skip points!
[DEBUG][bot #1][12/28 11:10:21 AM]: Injected 3 hit splat callbacks!
[DEBUG][bot #1][12/28 11:10:21 AM]: Injected 1 equipment callbacks!
[DEBUG][bot #1][12/28 11:10:21 AM]: Injected 1 login return code callbacks!
[DEBUG][bot #1][12/28 11:10:22 AM]: Loading RS world : 375
[iNFO][bot #1][12/28 11:10:22 AM]: Initializing 36 API modules...
[iNFO][12/28 11:10:22 AM]: Started bot #1
[iNFO][bot #1][12/28 11:11:10 AM]: [break Manager] After botting for 49 minute(s), you will break for 7 minute(s).
[iNFO][bot #1][12/28 11:11:10 AM]: Loaded 6 built-in random solvers!
[iNFO][bot #1][12/28 11:11:10 AM]: Error in script onStart(): ShinyFighterDEV
[iNFO][bot #1][12/28 11:11:10 AM]: Terminating script ShinyFighterDEV...
[iNFO][bot #1][12/28 11:11:10 AM]: Thank you for using ShinyFighter!
[iNFO][bot #1][12/28 11:11:10 AM]: Script ShinyFighterDEV has exited!
[iNFO][bot #1][12/28 11:11:10 AM]: Started script : ShinyFighterDEV

GUI:

java.awt.EventQueue.invokeLater(new Runnable() {
	@Override
	public void run() {
		GUI = new GUI();
		GUI_Initialized = true;
		GUI.setVisible(true);
	}
});
while (true) {
	if (GUI_Initialized && !GUI.isVisible()) {
		break;
	}
	sleep(100, 200);
}

Edited December 28, 201510 yr by Shiny

Are you running it from command line? Because "Error in script onExit():" should also print out the specific error in command line.

(Version 2.4.25)

 

Unfortunately this has started happening to my scripts too just got a bug report from a user

 

here is a screenshot

 

Are any of them by chance running it in command line? I really want that stack trace to figure out what's happening.

Maybe we need to make the logger show the stacktrace as well, but I am worried about information overload.

I am running it by command line always with -1255, never happens to me. Not sure about the users though, I will ask again if this ever happens, it only seems to affect a small amount of users

 

Apologies for the bug report, I really know how annoying they can be

Are you running it from command line? Because "Error in script onExit():" should also print out the specific error in command line.

It never print anything out. Not using command line.

I use to get these errors and I want to say that it usually the gui. If this error comes up more often then usual. Make a log on every statement and see which one doesn't show.

It never print anything out. Not using command line.

I use to get these errors and I want to say that it usually the gui. If this error comes up more often then usual. Make a log on every statement and see which one doesn't show.

 

catch (Exception e) {
    bot.getLogger().info("Error in script onExit(): " + script.getName());
    e.printStackTrace();
}

 

It definitely does print something if "Error in script onExit()" comes up.