You could try running it under gdb and see what filename.raw looks like.

Sure, but for that I'd need to run it under gdb everytime since I can't find how to reproduce. Or maybe I could patch the assert to dump hexa code of both version of filename... seems less annoying to do that. I'll try to fetch more info.

I have the same problem.

macOS Mojave

Solvespace opens other files correctly. Not this one though.

Does it always reproduce with that file? If so, can you upload it?

Yeah... I mean, I created it and modified it with Solvespace. But now it will crash the app totally!
Since I have Wine, I downloaded the exe file and it does work and can open the file without issue.

Anyway, while typing this, I made a quick test with the Windows exec and I found out the problem was with the force NURBS surfaces to triangle mesh option.
I simply opened the file with WINE, deselected the option, saved and it now works with Solvespace for macOS too.

Does it crash with the "Unexpected null byte in middle of a path." assertion on macOS for you?

I got mad. And very unhappy, because I love Solvespace.
Also, while trying a way to open the file, I tried to download the .dmg file from here and I found out that it still does not work “out of the box”. (I wanted to see if the issue happened with a fresh Solvespace app package too.)

The app does not quit itself. The rolling circle appears and the app does not respond. Everything freezes.

Anyway now the problem happened again but just by selecting the force NURBS surfaces to triangle mesh box.

The only way to stop it is to force close it.

If you don't upload the file that reproduces the bug (or otherwise provide a series of steps that leads to the crash) there is nothing I can do to fix it.

Yeah sure, may I send it to you privately?

Sure. whitequark@whitequark.org.

Okay, I got your file. Your crash is not related to this issue, and does not reproduce on master, so I suspect it has been fixed since 2.3. Annoyingly right now there's no easy way to get a recent .dmg but #618 should fix that.

Ok... so you suggest to compile a recent version?

Yep. I don't currently have a reasonably functional way to develop for macOS so I can't easily build it for you.

Hi,

I built Solvespace for macOS. The app package is in the bin folder. There is also the .dmg file. If you want I can upload the dmg to be put in GitHub Releases. Also, the dmg opens and Solvespace works without problems.

There is an issue though, the screen flashes continuously. flickers while moving the mouse cursor.

If you want I can upload the dmg to be put in GitHub Releases.

The files in GitHub Releases are populated exclusively by automated build scripts so that they are (in principle) reproducible by anyone who wants to ensure they're legitimate, and there is no chance that a developer uploads a binary infected by malware.

There is an issue though, the screen flashes continuously. flickers while moving the mouse cursor.

That's unfortunate. Someone with both Apple hardware and good understanding of macOS graphics would have to fix that.

Oh cool. I didn’t know that but I totally agree with that.

About the Mac issue, yeah. That’s very unfortunate. The old package does not do that though.

PS:
I like the old UI/color the most.

If I will care enough – lol –, I would like to port Solvespace to Mac OS X Tiger PowerPC.

The old package does not do that though.

Sure. The renderer was completely rewritten in the meantime for a variety of reasons so it's not trivial to determine what change causes the flickering. Moreover, the new renderer works just fine on any version of macOS I have access to (macOS 10.10 and later doesn't run well in a VM), so this issue also might be caused by a change in macOS.

I like the old UI/color the most.

The UI colors were changed to have higher contrast to aid visually impaired and colorblind users.

Oh...

@bmorel @mePy2 does the current edge macOS build crash as you described in this issue?
What about the "flickering"?
https://github.com/solvespace/solvespace/releases/tag/edge

@bmorel @mePy2 does the current edge macOS build crash as you described in this issue?
What about the "flickering"?
https://github.com/solvespace/solvespace/releases/tag/edge

Hi @ruevs I’m sorry for the late reply. I did’t forgot about it though.
I am going to try it as soon as possible. Thank you very much.

@ruevs It works. Thank you very much.
Would you mind telling me what the problem was?
Cheers

I don't know. Too many things have changed since 2.3, I don't have a Mac and the file you sent to Whitequark ;-)

I asked you to try since we now have an always fresh macOS build.

I hit this myself (on OSX, master build from yesterday) and what I think is happening is that in GraphicsWindow::PopulateRecentFiles(), the call to SS.OkayToStartNewFile() can potentially update recentFiles, which invalidates the path reference - which will only break things if the path actually moves in the vector, which explains why it doesn't reproduce all the time.

My steps to reproduce are:
Open File1. Make some changes to it
Open File2 from the Open Recent menu. When asked whether to save changes to File1, click Save.
Do this a couple of times (maybe the number of elements in the recents list is a factor, or which element you open) and you'll hit that assert eventually.

I'll open a PR shortly.