2013-06-15 14:32:48 -0500 | received badge | ● Famous Question (source) |
2013-05-29 10:35:49 -0500 | received badge | ● Notable Question (source) |
2013-05-23 10:58:44 -0500 | commented question | Spawning PR2 makes Gazebo die with Illegal Instruction Any clue ? |
2013-05-22 17:41:50 -0500 | received badge | ● Popular Question (source) |
2013-05-21 07:32:02 -0500 | received badge | ● Citizen Patrol |
2013-05-15 08:37:54 -0500 | asked a question | Spawning PR2 makes Gazebo die with Illegal Instruction Hello, Just got a strange problem yesterday when trying to launch Gazebo and PR2 to test a new stack. The symptoms look quite frequent but the causes appears to be various, so I'm opening a new thread for that. Under ROS Fuerte and Ubuntu 10.04, I roslaunch emptyworld environment with emptyworld.launch. Everything looks right at this time. Then, I try to spawn the PR2 through "pr2.launch" file. The PR2 visually appears, but at some point, Gazebo crashes and PR2 node (defaultcontrollersspawner) also. I still got the Gazebo GUI and can manipulate the robot (move it in the environment) but I can't spawn other objects neither control the PR2. The error I get from Gazebo is an "Illegal Instruction" (logs are enclosed at the bottom of the question). On answers.ros.org, I found that a similar issue was due to SSE compilation process, but that may have been solved with Gazebo 1.6.15 (I'm using 1.6.16). Here I read about a Graphical Card driver that was conflicting ( http://answers.gazebosim.org/question/658/gazebo-pr2-getting-stuck-at-launch/ ) but as it is a ROS Groovy issue and my Gazebo is launching well, I'm not sure it can apply. I updated Linux with the recommended updates and ros with the corresponding patches on the beginning of May. As I didn't used ROS since Monday 6th, that may be part of the explanation. Does somebody have an idea of what's going wrong with PR2 ? I can still spawn simple boxes in the environment. Thanks for reading ! EDIT : Any advice ? Here are the logs : renaudo@oogawa:~/rosworkspace$ roslaunch gazeboworlds empty_world.launch (more) |
2013-04-11 08:24:26 -0500 | received badge | ● Famous Question (source) |
2013-03-08 11:24:31 -0500 | received badge | ● Notable Question (source) |
2013-02-12 19:50:38 -0500 | received badge | ● Popular Question (source) |
2013-02-12 04:21:03 -0500 | answered a question | [solved] Jpeg file make Gazebo die Ok, got the problem and (probably) the solution. The case is quite the same as what's described in : Answers ROS Ogre Exception The computer I'm using have only a graphic chipset and no graphic card. My hypothesis is that loading images exceed the video memory available on the chipset (images were 4000x2000px). I resized my images and I have no problem anymore. As a conclusion : Always be careful about the usage of memory when you're using graphical elements. |
2013-02-12 03:03:49 -0500 | received badge | ● Editor (source) |
2013-02-11 10:47:59 -0500 | asked a question | [solved] Jpeg file make Gazebo die Hello, I'm currently re-using some old code developed under ROS Electric with ROS Fuerte. Especially, I'm spawning in Gazebo a customized wall+photo environment described in a urdf file. I defined my own Material, for example : Around every wall spawn correctly with the photo applied as texture. But on two photos (sima-south-left.jpg and sime-south-right.jpg), the texture isn't found and Gazebo die with error : I don't get why two specific images are making Gazebo die. Are there max/min size on texture we can use ? All images are in jpg and located in the same folder. This code was working with Electric. Any advice would be welcome. Thanks for reading. EDIT : I tried with some others random pictures from internet, and I have no problem to map them on walls ... that's quite strange that two specific pictures are making gazebo crash ... |