[Fixed] "gzdoom" received signal SIGFPE, Arithmetic exception

Bugs that have been investigated and resolved somehow.

Moderator: GZDoom Developers

Re: "gzdoom" received signal SIGFPE, Arithmetic exception

Postby Graf Zahl » Tue Oct 15, 2019 2:53 am

I just committed a refactor of the music playback interface and used the new top level functions to add proper synchronization. Turned out it was never done properly - there were various mutexes deeper in the music code but they didn't cover everything that was needed. It also turned out that better all interface functions try to lock the mutex because with the exception of two simple getters they all can change state which shouldn't overlap with producing output data.

This needs a bit of testing, so far it's in a work branch.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: "gzdoom" received signal SIGFPE, Arithmetic exception

Postby _mental_ » Tue Oct 15, 2019 4:26 am

ZMusic_Close() tries to delete a locked mutex. I think there is no need to lock here as long as the song is stopped.
_mental_
 
 
 
Joined: 07 Aug 2011

Re: "gzdoom" received signal SIGFPE, Arithmetic exception

Postby Graf Zahl » Tue Oct 15, 2019 5:11 am

Correct, but in this case the client side pointer needs to be nulled before taking down the object.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: "gzdoom" received signal SIGFPE, Arithmetic exception

Postby Graf Zahl » Tue Oct 15, 2019 10:57 am

I hope it's fixed with my recent changes. Waiting for confirmation.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Re: "gzdoom" received signal SIGFPE, Arithmetic exception

Postby mwnn » Tue Oct 15, 2019 11:44 am

Graf Zahl wrote:I hope it's fixed with my recent changes. Waiting for confirmation.
So I've built a debug build of the zmusic_interface branch.
Copied the soundfonts to .config/gzdoom/soundfonts and run the game.
Set Fatboy as the active soundfont and let it run the main menu loop for about 5 minutes without hitting a key and it didn't blow up on me.
I'll continue to try that a few more times.
I think that's 3/3 solved.

The fluidsynth warnings which occasionally appear in the terminal i.e:
Code: Select allExpand view
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
Look like nonsense - how can that be an issue with 8GB of RAM + 2GB swapfile?

EDIT: Not very exciting viewing but here you go:
https://drive.google.com/file/d/1LDuF_c ... sp=sharing
Skip to 4:40 to see the settings in use.
Before these changes it was lucky to last more than a minute or two.
mwnn
 
Joined: 04 Oct 2019
Location: Manchester; England
Operating System: Debian-like Linux (Debian, Ubuntu, Kali, Mint, etc) 64-bit
Graphics Processor: ATI/AMD with Vulkan Support

Re: "gzdoom" received signal SIGFPE, Arithmetic exception

Postby _mental_ » Tue Oct 15, 2019 1:01 pm

mwnn wrote:The fluidsynth warnings which occasionally appear in the terminal i.e:
Code: Select allExpand view
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
Look like nonsense - how can that be an issue with 8GB of RAM + 2GB swapfile?

It’s normal to get this warning on Linux. Locking memory pages to RAM requires special privileges that executables don’t have by default.
_mental_
 
 
 
Joined: 07 Aug 2011

Re: "gzdoom" received signal SIGFPE, Arithmetic exception

Postby Chris » Tue Oct 15, 2019 1:45 pm

_mental_ wrote:
mwnn wrote:The fluidsynth warnings which occasionally appear in the terminal i.e:
Code: Select allExpand view
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
Look like nonsense - how can that be an issue with 8GB of RAM + 2GB swapfile?

It’s normal to get this warning on Linux. Locking memory pages to RAM requires special privileges that executables don’t have by default.

Individual processes can also be limited in the amount of memory they can lock to RAM, to prevent a single app from hogging too much.
User avatar
Chris
 
Joined: 17 Jul 2003

Re: "gzdoom" received signal SIGFPE, Arithmetic exception

Postby Graf Zahl » Tue Oct 15, 2019 2:01 pm

The problem here is that they dared to print this piece of nonsense in the first place. It's ok trying to lock memory but considering it warning worthy if it can't be done is another story.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
 
Joined: 19 Jul 2003
Location: Germany

Previous

Return to Closed Bugs

Who is online

Users browsing this forum: No registered users and 0 guests