@kas1e

Quote:

Could you post a video or screenshot of this?

@jabirulo

Just a quick question : Are you letting the child finish before exiting?

@jabiruolo

It is really strange, because I have commented out every call to Enable() and Disable(). I will need a working machine to test.

@jabirulo

Hmm. Strange. I am not sure, I can fix that without having a machine to run it.

@jabirulo

And now? Spotless

@kas1e

A friend of mine picked up a new power supply from the mail. We will try to install it asap.

@kas1e

This is my attempt at fixing first two issues from your post. Last two, I am not sure what to do about.

Spotless : Download from Drive

@kas1e

Thanks for the reports. As you might guess, I cannot do so much at the moment. I will save info and work when possible.

Fresh version with a registers pane. Untested.

Spotless without prints and with registers pane

@kas1e

Quote:

Are you serious??! Whupti-woo!

No, it is not because of the prints. It is because I understand, what is wrong :).

I will do a freshly cleaned version in just a bit. Sadly I have no other Amiga hardware. I am trying to repair it with a new power supply together with a friend. If unsuccessfully, I will have to buy new hardware.

New test candidate : Spotless test alpha 02

@kas1e

I did change something, and was expecting it to perform Better. I have one last change, I want to do, and then remove the console output. If we are lucky, this is going to do the trick.

@kas1e

But before you said, that there was some improvement?? If there is no improvement with this version, then I have no idea what to do.

@walkero

I am quite sure, that it is a fatal wound (the x5000). I am communicating with Amigakit, but apparently they haven't got so many options at the moment.

@thread

Ok, so I might explain. The idea is, that perhaps the reading of context info on a running child could be responsible for the crashes. Usually, if you have a shared ressource and multiple reads at the same time, it will screw up. Also, it might give bad results, even if it succeeds. I think, I might have closed one of the gaps for this scenario. There might be a small case left. If I can manage to close this, my hope is, that we will have solved this crash scenario.

I just came back from the hospital with a lung problem. Now I am in a summer house with some friends. When I get back Saturday, I might be able to do a fresh version. But of course I can't test it myself, since my x5000 is dead

Any news on the latest version?

@afxgroup

I had to go to the hospital with a bad lung. And I forgot to cut the power. So it had been on for 6 days non-stop, and probably som circuitry overheated.

My X5000 died again.

@kas1e

New link

Fresh version updloaded (same link). Please report back, if it still crashes and if you get something new on the serial. Hopefully we can track something.