Segmentation fault when robots with Lua controllers are selected about argos3 HOT 9 CLOSED

I'll look into it. Is this related to the selection bug that is already open? That is due to the Intel driver managing badly multiple graphics cards. The solution is likely to disable the Intel graphics card from the BIOS.

from argos3.

@alanmillard could you check if you have lua_editor="true" set inside the OpenGL tag?

from argos3.

Never mind, I see you do have this variable set from core_dump/obstacle_avoidance.argos. This indeed seems like it may be a duplicate of #40 then.

from argos3.

This certainly looks like it may be a duplicate of #40.

Let me know if there are any tests that I can run for you on this system to provide further information that may be of use.

from argos3.

Try disabling the Intel video card. Unfortunately there isn't much I can do :(

from argos3.

@ilpincy is it possible to propose a series of tests that we can use to probe this issue a little bit deeper? It would be good if we can collaborate and get #40 resolved at some point.

From my testing, it seems that the entities are being drawn in the selection buffer such that they are offset from what is being drawn in the display buffer. This corruption becomes apparent when the makeCurrent() and doneCurrent() lines are removed. So at a best guess on my end, the segfault is a result of calling the makeCurrent() and doneCurrent() functions when drawing incorrectly inside the selection buffer...

from argos3.

I doubt the bug is due to code in ARGoS. If so, it would happen on other Linux boxes, other drivers, etc. It only happens with a specific driver on machines that have multiple graphics cards.

from argos3.

from argos3.

Good to know, it doesn't happen on my old laptop which also has a single Intel card. It's still driver specific though.

from argos3.