MGI

When it is fully stable. Until then, please use something like https://www.proxifier.com/

As always, please update your mirrorclient.jar mirrorclient.zip Major fixes include: Bot jvm running out of memory after some time and crashing Some cases of widget visibility methods returning true when not actually visible Client lag after mirror client is closed New features include: Updated for rs #75 Implemented hooks for latest api features (such as GE) To be fixed in next version (1.05): Object spawns/despawns appear delayed to the scripts.

Somewhat around this weekend.

is ur ram dual channel?

Those are model buffers (this time they are causing problems on osbot side), will be fixed in v1.04

Could you make a heap dump of osbot jvm just before it is about to crash, compress it and upload it somewhere? (do not post the link here, pm it instead, as the heap dump will contain sensitive information such as your osbot password).

Looks like a serious issue, have you had any other exceptions before this? Especially something like "Read timeout"

How much memory is allocated for osbot? It is possible that osbot itself runs out of memory.

Most likely the lag is because you are running windows under virtualbox.

Does this issue occur with normal mode too?

Run osbot in debug mode, and post your console output.

There is currently small delay before changes like object spawned/deleted reach mirror client, which is due to data caching. Will be fixed on 1.04

You can use a solution like https://www.proxifier.com/ while we implement proxying if you really want to try it asap.

As always, please update your mirrorclient.jar mirrorclient.zip Major fixes include: Objects disappearing after entering new region Not being able to start multiple bot tabs with mirror mode Bot/Webclient freezing after one of them is closed Double key typing issue Possibly more New features: Very low CPU mode (Expermental, enable under performance debugging options)

The update is almost ready.

"org.osbot.BotApplication m"

Most likely osbot is running on 32 bit java

A fix for this is underway, new build will be released later today.

A fix for this is being developed.

Attaching while logged in is still not fully supported yet.

were you already logged in when you loaded it?

Everytime you enter a new region? or just randomly

compare the size of the jar

were you using v1.02?

was fixed.