Home
SOMETHING IS WRONG SOMETHING IS WRONG SOMETHING IS WRONG Mac OS

SOMETHING IS WRONG SOMETHING IS WRONG SOMETHING IS WRONG Mac OS

May 30 2021

SOMETHING IS WRONG SOMETHING IS WRONG SOMETHING IS WRONG Mac OS

Ok, I just downloaded 0.14.0.178, and that one does not crash either.

Here’s what you do when you see a folder with a question mark on a Mac: 1. Shut down the Mac by holding down the power key a few seconds. Hold down COMMAND-R and press the power button. Continue holding down COMMAND-R until you see the Apple me.

Hi @jenskyverge,. Thanks for your fast response. I followed your advice and spent some time with the old plugin (v1.11.4) and it worked well. The plugin version for me is not so important if the pixel works properly. I was trying to get things worked with your tutorial, but something went wrong. Could you please assist me in doing it? This is the case: HP Pavilion DV1000, with Intel Extreme Graphics 2. Mac OS X Leopard iAtkos v7, updated to 10.5.8 VGA VESA 3.0 as you may know, there are no real VGA driver for this VGA since 10.5.x. Saying 'something's wrong with Siri' on a command to set a timer is like saying 'something's wrong with Google' on a search result. It's just bits of data from an enormous server farm. The problem isn't them.

But I can confirm the crash happening in the latest one as of right now (0.14.0.238). All I do is double click on openMSX.app (it launches by default with C-Bios), and then click on the top-left 'menu' -> 'Hardware...' -> 'Change Machine...', and then whichever machine you select, it just crashes.

Crash report:

Thanks!

Please install a debug build: https://openmsx.fixato.net/builds/mac/debug-builds/x86_64/
Then the crash report is most useful with such builds, as it will contain the full stack trace.

Does it crash if you have the ROMs for the machine you are switching to?
Does it crash if you use the SDL renderer? (A stack trace of someone else suggests it is related to that.)

It is strange that it doesn't crash in 178 for you, although it did for FX. Santi, can you bisect which version starts to crash for you, using the available builds on Fixato's site?

Sure thing! Will try this tomorrow and get back to you!

Ok, this is the crash log for version 238 (debug):

Also, while trying older versions. The first one that crashes is 198. From 190 backwards, it does not crash for me. It does not seem to make a difference which machine do I select. It crashes even changing from one C-Bios to another.

Also, not sure if this matters, but I've also noticed that from version 198 onwards, some machines appear duplicated on the list of hardware, for example, see this screenshot where the MSX1 and MSX2 CBios machines appear twice:

That does not happen from 190 backwards.

Something Is Wrong Something Is Wrong Something Is Wrong Mac Os Catalina

Thanks! Does it crash if you use the SDL renderer?

Something is wrong something is wrong something is wrong mac os 11

Yep, the same thing happens, here's the debug report:

But something weird is happening, since actually it also crashes when I try to change the renderer directly from within OpenMSX, when I type 'set renderer SDL', it crashes. To change the renderer, I had to open a previous build, then change it and 'save_settings'. Looking at the debug log, the crash occurs exactly in the same place (the destructor of SuperImposedFrame). It also crashes when trying to quit openMSX. So, something changed in version 198 that made the Mac build generally unstable for some reason.

So, the problem seems to basically be when the graphic renderer is being destroyed. Since this happens either when changing machines, changing renderer or quitting openMSX, that's why I see crashes in all these instances.

But I was looking at the source code of openMSX (first time in my life looking at it, so, don't take my reading very seriously ). And the destructor of SuperImposedFrame (or rather the one of its super class, since SuperImposedFrame doesn't have one explicitly defined) looks very innocent to me. So, the problem is probably somewhere else, maybe in the PostProcessor, or the Rasterizer that maybe are freeing something twice?

Some things have been changed which may fix it. Please try again tonight at about 22:05 (CET), when the build server built a new build

Just tested it with version 249, no crash this time!!!

- I can switch machines without a crash
- I can switch renderers without a crash
- There are no repeated machine names anymore!

So, at least in my machine, this issue is fixed

Something Is Wrong Something Is Wrong Something Is Wrong Mac Os Download

Page 2/3
1 3
Login or register to post comments

SOMETHING IS WRONG SOMETHING IS WRONG SOMETHING IS WRONG Mac OS

Leave a Reply

Cancel reply