e-uae crashes on multicore cpus (64bit)

[Herr Irrtum]

This is what happens most of the time (terminal output):
---------------------------------------------------------------
~$ e-uae
E-UAE 0.8.29-WIP4
Build date: Jun 8 2010 05:19:30
SDLGFX: Initialized.
SDLGFX: Using SDL version 1.2.14.
SDLGFX: Display is 32 bits deep.
SDLGFX: Found screenmode: 2048x1152.
SDLGFX: Found screenmode: 1920x1080.
SDLGFX: Found screenmode: 1776x1000.
SDLGFX: Found screenmode: 1680x1050.
SDLGFX: Found screenmode: 1440x900.
SDLGFX: Found screenmode: 1400x1050.
SDLGFX: Found screenmode: 1280x1024.
SDLGFX: Found screenmode: 1280x960.
SDLGFX: Found screenmode: 1280x800.
SDLGFX: Found screenmode: 1280x768.
SDLGFX: Found screenmode: 1280x720.
SDLGFX: Found screenmode: 1152x864.
SDLGFX: Found screenmode: 1152x648.
SDLGFX: Found screenmode: 1024x768.
SDLGFX: Found screenmode: 800x600.
SDLGFX: Found screenmode: 720x480.
SDLGFX: Found screenmode: 640x480.
Found 1 joystick(s)
Found x11pc raw keyboard mapping
Using cooked keymap
Opening cfgfile '/home/xxxxxxxxxxx/.e-uaerc'...okay.
Testing the RDTSC instruction ... done.
TSC frequency: 2672,500000 MHz
Found x11pc raw keyboard mapping
Using cooked keymap
Speicherzugriffsfehler
~$ # comment: it did not start at all
---------------------------------------------------------------

"Speicherzugriffsfehler" means more or less "memory access error".

I found out what caused this:
It's my Intel i7 multicore CPU (4 real cores, 4 virtual cores).
If I run a multi threaded application (like i.e. handbrake) in the background, than e-uae starts without any problem. If there is no application running, e-uae crashes.
Conclusion: Seems like limiting the CPU power helps e-uae.

So the trick is, to force e-uae to only 1 core. Lets say Core no. 4:
Than the command should be:

taskset -c 3 e-uae

(find more about taskset within it's man-page; cpu count starts with 0).
Now the trick is for the packager: Either compile it in a way that it only uses one core, or does not crash when using multiple cores. Or build a little #!/bin/sh script which starts it with taskset (obviously "taskset -c 0 e-uae" would bring you to the save side. Having taskset as a dependency and checking+greping /proc/cpuinfo should help to determine, it it's a multicore cpu at all should make it more perfect :) )

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: e-uae 0.8.29-WIP4-10
ProcVersionSignature: Ubuntu 2.6.38-11.49-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Mon Sep 12 23:09:17 2011
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: e-uae
UpgradeStatus: Upgraded to natty on 2011-07-30 (44 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[EricDHH (ericdhh)]

In 12.04 amd64 with newer version this exists on, will we see a bugfix?

e-uae 0.8.29-WIP4-10

SDLGFX: Found screenmode: 640x480.
Found 0 joystick(s)
Found x11pc raw keyboard mapping
Using cooked keymap
Opening cfgfile '/home/eric/.e-uaerc'...failed
Opening cfgfile '.e-uaerc'...failed
Testing the RDTSC instruction ... done.
TSC frequency: 2813,000000 MHz
Found x11pc raw keyboard mapping
Using cooked keymap
`menu_proxy_module_load': e-uae: undefined symbol: menu_proxy_module_load

(UAE:3778): Gtk-WARNING **: Failed to load type module: (null)

`menu_proxy_module_load': e-uae: undefined symbol: menu_proxy_module_load

(UAE:3778): Gtk-WARNING **: Failed to load type module: (null)

Speicherzugriffsfehler (Speicherabzug geschrieben)

[Selmi (selmi)]

crashes on 12.04 with repository version and taskset workaround doesn't help

[Faserbuendel (faserbuendel)]

same here, 12.04 repository version crashes with "segmentation fault" also with taskset workaround

[Christian Kirbach (christian-kirbach-e)]

Still segmentation fault with Ubuntu 12.10

[1448412 (uli-rgbg)]

Hi,

still segfaults in 13.10