exe crash at the beginning

Bug #1504819 reported by emmanuel
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ember
Confirmed
Undecided
Unassigned

Bug Description

there the output:

Starting Ember....
Registering: list_commands
Registering: quit
Registering: toggle_erispolling
Starting Ember version 0.8.0
Initializing Ember services
Registering: loadscript
Registering: connect
Registering: meta_refresh
Registering: meta_abort
Metaserver Service created
Registering: set_value
Registering: get_value
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
  Major opcode of failed request: 155 (DRI2)
  Minor opcode of failed request: 3 (DRI2CreateDrawable)
  Resource id in failed request: 0x4200002
  Serial number of failed request: 31
  Current serial number in output stream: 33
AL lib: ReleaseALC: 1 device not closed

Revision history for this message
Erik Ogenvik (erik-ogenvik) wrote :

Could you provide your ~/.local/share/ember/ember.log file?

Revision history for this message
emmanuel (emmanuel-tuloup) wrote :

thanks for your answer

there the file, but this morning there wasn't this error again

perhaps a standby mode/wake up of the system has changed somethings ?

i've succeded in create a character and walk, but the terrain isn't there:
i can see trees, houses, grass, flowers, characters, but not the terrain (static meshes ?)

that was for the compiled ember on my system (v1.8)

for the donwloaded version, there is an error:
emmanuel@vestibule:/media/emmanuel/ce72ce91-e57a-47d5-a6a5-ebf8dc2f2d54/EMBER/hammer/work/local/bin$ /home/emmanuel/Téléchargements/ember-0.7.2.1-x86_64
Starting Ember....
Registering: list_commands
Registering: quit
Registering: toggle_erispolling
Starting Ember version 0.7.2
Initializing Ember services
Registering: loadscript
Registering: connect
Registering: meta_refresh
Registering: meta_abort
Metaserver Service created
Registering: set_value
Registering: get_value
Setting home directory to /home/emmanuel/.ember
libGL error: dlopen /usr/lib/x86_64-linux-gnu/dri/r600_dri.so failed (/usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1: undefined symbol: drmPrimeHandleToFD)
libGL error: dlopen ${ORIGIN}/dri/r600_dri.so failed (${ORIGIN}/dri/r600_dri.so: cannot open shared object file: No such file or directory)
libGL error: dlopen /usr/lib/dri/r600_dri.so failed (/usr/lib/dri/r600_dri.so: cannot open shared object file: No such file or directory)
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
Crashed with signal 11, will try to detach the input system gracefully. Please report bugs at https://bugs.launchpad.net/ember
Erreur de segmentation (core dumped)
emmanuel@vestibule:/media/emmanuel/ce72ce91-e57a-47d5-a6a5-ebf8dc2f2d54/EMBER/hammer/work/local/bin$

thanks

Revision history for this message
emmanuel (emmanuel-tuloup) wrote :

i give precision about that i've compiled the ogre 1.9 source from bitbucket some days ago directly, into another directory,
and develop a little application that use OgreBullet, load some meshes, create some bullet objets into the world, created a sun that revolve around my world and create shadows

and i've never met this problem with my driver r600

Revision history for this message
emmanuel (emmanuel-tuloup) wrote :
Revision history for this message
emmanuel (emmanuel-tuloup) wrote :

well i've relaunched the compiled version 0.8, and the error reappears
there the log

Revision history for this message
Erik Ogenvik (erik-ogenvik) wrote :

This error is unfortunately caused by bad drivers. I.e. the low level drivers that supply the OpenGL functionality are broken, and will in some cases result in a crash. We've seen this before with Mesa-drivers on both AMD and Intel.

The only recommended solution is to try with other drivers. Perhaps the proprietary provided by AMD if possible, or other open source ones. I'm not that well verses with the AMD driver eco system to provide a better answer.

Revision history for this message
Erik Ogenvik (erik-ogenvik) wrote :

Marking this as confirmed, although it's not a bug in either Ember or Ogre (which is the 3d graphics library we use).

Changed in ember:
status: New → Confirmed
Revision history for this message
emmanuel (emmanuel-tuloup) wrote : Re: [Bug 1504819] Re: exe crash at the beginning

Hello again,

is there some doc to learn how the code source is organized ?
I would like to add the behaviour of natural life : animals and trees
from wich source file the ogre meshes are imported ?

i've read some source into:
hammer/work/source/worldforge/clients/ember/src/components/ogre/

the web site tell about "Plants grow and wither. Animals roam the world,
eating and getting eaten."
where is this code ?

i've intregrated bullet into my little ogre application, are you interested
into integrating bullet into worldforge ?
into cypheris or ember ? i'am a little bit lost about what module do what,
cypheris is the server and manage network communication, but where is a
character manager into it ?

2015-10-11 15:11 GMT+02:00 Erik Ogenvik <email address hidden>:

> Marking this as confirmed, although it's not a bug in either Ember or
> Ogre (which is the 3d graphics library we use).
>
> ** Changed in: ember
> Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1504819
>
> Title:
> exe crash at the beginning
>
> Status in Ember:
> Confirmed
>
> Bug description:
> there the output:
>
> Starting Ember....
> Registering: list_commands
> Registering: quit
> Registering: toggle_erispolling
> Starting Ember version 0.8.0
> Initializing Ember services
> Registering: loadscript
> Registering: connect
> Registering: meta_refresh
> Registering: meta_abort
> Metaserver Service created
> Registering: set_value
> Registering: get_value
> X Error of failed request: BadDrawable (invalid Pixmap or Window
> parameter)
> Major opcode of failed request: 155 (DRI2)
> Minor opcode of failed request: 3 (DRI2CreateDrawable)
> Resource id in failed request: 0x4200002
> Serial number of failed request: 31
> Current serial number in output stream: 33
> AL lib: ReleaseALC: 1 device not closed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ember/+bug/1504819/+subscriptions
>

--
Emmanuel TULOUP

Revision history for this message
Erik Ogenvik (erik-ogenvik) wrote :

Worldforge is made up of a lot of different components, so it's not always clear on where to start.

The wiki has a lot of useful content, but it's also a bit disorganized. But do check it out: http://wiki.worldforge.org/wiki/Main_Page

Here's a quick overview of the various Worldforge libs: http://wiki.worldforge.org/wiki/Ember_development#Worldforge_libraries

Regarding Ember and Cyphesis it's worth knowing that the server (Cyphesis) is authoritative in everything. So any behaviour or rule is always placed on the server.
The code for Plants for example is contained in Cyphesis, more specifically in the "ruleset" module.

We do have an ongoing project for integrating Bullet into the system, starting at Cyphesis. Do you have any example of the work you've done with Bullet?

Revision history for this message
emmanuel (emmanuel-tuloup) wrote :

ok, i'm going to read this as soon as i have some free time.

yes there my little application:
https://bitbucket.org/emmanuel1359/heightmapterrain/src

i've integrated bullet with an heightmapped terrain,
and tried to do the same thing with a TerrainVolume (i would like to dig
the terrain, to find some ore...)

2015-10-14 10:53 GMT+02:00 Erik Ogenvik <email address hidden>:

> Worldforge is made up of a lot of different components, so it's not
> always clear on where to start.
>
> The wiki has a lot of useful content, but it's also a bit disorganized.
> But do check it out: http://wiki.worldforge.org/wiki/Main_Page
>
> Here's a quick overview of the various Worldforge libs:
> http://wiki.worldforge.org/wiki/Ember_development#Worldforge_libraries
>
> Regarding Ember and Cyphesis it's worth knowing that the server (Cyphesis)
> is authoritative in everything. So any behaviour or rule is always placed
> on the server.
> The code for Plants for example is contained in Cyphesis, more
> specifically in the "ruleset" module.
>
> We do have an ongoing project for integrating Bullet into the system,
> starting at Cyphesis. Do you have any example of the work you've done
> with Bullet?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1504819
>
> Title:
> exe crash at the beginning
>
> Status in Ember:
> Confirmed
>
> Bug description:
> there the output:
>
> Starting Ember....
> Registering: list_commands
> Registering: quit
> Registering: toggle_erispolling
> Starting Ember version 0.8.0
> Initializing Ember services
> Registering: loadscript
> Registering: connect
> Registering: meta_refresh
> Registering: meta_abort
> Metaserver Service created
> Registering: set_value
> Registering: get_value
> X Error of failed request: BadDrawable (invalid Pixmap or Window
> parameter)
> Major opcode of failed request: 155 (DRI2)
> Minor opcode of failed request: 3 (DRI2CreateDrawable)
> Resource id in failed request: 0x4200002
> Serial number of failed request: 31
> Current serial number in output stream: 33
> AL lib: ReleaseALC: 1 device not closed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ember/+bug/1504819/+subscriptions
>

--
Emmanuel TULOUP

Revision history for this message
Jonathan Deeds (jonathandeeds) wrote :

I have confirmed this with Xubuntu 14.04.3 LTS on three different hardware platforms (eMachines, HP Proliant, and a more modern HP with quad processor and 8 GB RAM), so I think it needs addressing. As emmanuel is mentioning, many other applications are working fine with OpenGL (e.g. Blender). I would like to try any help diagnose and solve this bug, so am setting up a fresh system on the hardware that fails... more to come.

Revision history for this message
Jonathan Deeds (jonathandeeds) wrote :

The seg fault crash occurs when either of the following functions are called inside Ogre for the first time. The OpenGL documentation says the arguments are valid, although not sure why one is trying to unbind before anything has happened yet.

Function GLStateCacheManagerImp::initializeCache()

        glBindFramebuffer(GL_FRAMEBUFFER, 0);

        glBindRenderbuffer(GL_RENDERBUFFER, 0);

This crash happens even with Ogre's Wiki - Basic Tutorial 1. However if I rebuild Ogre with these two lines commented, the tutorial runs, and I get about 300 FPS.

Ember runs also up to the point of rendering a blank screen after the settings and login as admin. This might be due to some other misconfiguration on my part, but looks hopeful.

Revision history for this message
Jonathan Deeds (jonathandeeds) wrote :

Checking the Open GL documentation and my Open GL version on the test machine, I see that these functions are not supported until Open GL 3.0, but my test machine is running Open GL 2.1.

glxinfo gives OpenGL version string: 2.1 Mesa 10.5.9

I guess Ogre really should check the Open GL version level before trying to call functions that are not implemented.

My choices are probably two: 1) find an older version of Ogre that works with Ember (unlikely), or 2) try the proprietary drivers to see if it can raise the Open GL version to 3.0 or higher.

Revision history for this message
Erik Ogenvik (erik-ogenvik) wrote :

NIce find. You should really report this issue on the OGRE forum.

Revision history for this message
Tuomas Lähteenmäki (lahtis) wrote :

Starting Ember....
Registering: list_commands
Registering: quit
Registering: toggle_erispolling
Starting Ember version 0.7.2
Initializing Ember services
Registering: loadscript
Registering: connect
Registering: meta_refresh
Registering: meta_abort
Metaserver Service created
Registering: set_value
Registering: get_value
Setting home directory to /home/valvoja/.ember
AL lib: oss.c:169: Could not open /dev/dsp: No such file or directory
Crashed with signal 11, will try to detach the input system gracefully. Please report bugs at https://bugs.launchpad.net/ember
Error de segmentation (core dumped)

Revision history for this message
Erik Ogenvik (erik-ogenvik) wrote :

Regarding #15, this is a separate issue. Could you report this as a new bug?
It seems like the main issue is that if we can't access the sound card (for whatever reason, including there being no installed sound card) Ember crashes.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.