Opened 5 years ago

Last modified 7 months ago

#2379 new defect

g.gui.animation causes fatal IO error 11 (Resource temporarily unavailable) on X server

Reported by: wenzeslaus Owned by: grass-dev@…
Priority: normal Milestone: 7.2.4
Component: wxGUI Version: svn-trunk
Keywords: crash, data loss, rendering, m.nviz.image, 3D, g.gui.animation, d.rast Cc:
CPU: Unspecified Platform: Linux

Description

Time to time g.gui.animation crashes the the whole user graphical session. The error is appearing randomly and I'm not able to reproduce it now although I got it yesterday and few months ago, too.

I got the error with different data and on two different computers (on Fujitsu laptop another Dell desktop) both running Ubuntu 14.04 with Unity (which uses Compiz). I think that few months ago I got it also with Ubuntu 12.04.

The results seems to be different. Once the session was frozen but the computer was running. Another time the graphical session was ended and login screen appeared.

I got the error when I had two animations in the animation tool but I'm not sure if this is really the cause. I'm also not sure if the problem is in 2D rendering, 3D rendering or wxPython. For example, it seemed to me that it is related to m.nviz.image but one 3D animation was rendered successfully and adding second animation which was 2D caused the crash.

Here are the last error messages are (obtained by redirecting to a file). Honestly, I'm not sure if I used only DEBUG=5 or also WX_DEBUG=5. This is few months old when I was able to repeated more than once. I'm not able to reproduce it now, although I got it.

...
D1/5: grass.script.core.start_command(): m.nviz.image --o transparency_value=0 position=0.58,0.87 format=ppm light_ambient=100 resolution_fine=1 light_color=255:255:255 light_position=0.2,-0.79,0.98 focus=2039,795,650 shininess_value=60.0 twist=0 bgcolor=255:255:255 color_map=elevlid_hourly_172_glob_11.50@foss4g_solar perspective=19 elevation_map=elevlid_10_20_3ft@cc_lidar2013_solar output=/media/.../grassdata/nc_spf/foss4g_solar/.tmp/vubu32/4374.0/b64a48a130d2926bd13099cf559930db3fa3756d light_brightness=36 height=4985 zexag=1.0 size=796,472
D1/5: grass.script.core.start_command(): m.nviz.image --o transparency_value=0 position=0.58,0.87 format=ppm light_ambient=100 resolution_fine=1 light_color=255:255:255 light_position=0.2,-0.79,0.98 focus=2039,795,650 shininess_value=60.0 twist=0 bgcolor=255:255:255 color_map=elevlid_hourly_172_glob_11.00@foss4g_solar perspective=19 elevation_map=elevlid_10_20_3ft@cc_lidar2013_solar output=/media/.../grassdata/nc_spf/foss4g_solar/.tmp/vubu32/4374.0/aaf4dea3de504f40a5e251276126643357fac133 light_brightness=36 height=4985 zexag=1.0 size=796,472

...


D3/5: GS_ready_draw
D3/5: GS_get_zrange(): min=280.89 max=503.013
D3/5: GS_get_aspect(): left=0, right=795, top=471, bottom=0
D3/5: GS_get_zrange(): min=280.89 max=503.013
D3/5: GS_done_draw
D3/5: GS_done_draw

GRASS_INFO_MESSAGE(4462,4): m.nviz.image complete. File </media/.../grassdata/nc_spf/foss4g_solar/.tmp/vubu32/4374.0/f27c2642e0e5d71fbba04e6551611f507e5fe06a.ppm> created.
GRASS_INFO_END(4462,4)
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
      after 562 requests (562 known processed) with 0 events remaining.

D2/5: G_file_name(): path = /media/.../grassdata/nc_spf/foss4g_solar
D2/5: G_file_name(): path = /media/.../grassdata/nc_spf/foss4g_solar

I wanted to collect more information before reporting but now I got it on different machine and I was not able to get more information. First I also thought that it is a local hardware problem but now I got it with different machine, although both are running the same system, Ubuntu 14.04.

Change History (7)

comment:1 Changed 4 years ago by neteler

Milestone: 7.1.07.2.0

Milestone renamed

comment:2 Changed 3 years ago by neteler

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:3 Changed 3 years ago by martinl

Milestone: 7.2.17.2.2

comment:4 Changed 2 years ago by neteler

Milestone: 7.2.27.2.3

Ticket retargeted after milestone closed

comment:5 Changed 20 months ago by martinl

Milestone: 7.2.3

Ticket retargeted after milestone closed

comment:6 Changed 20 months ago by martinl

Milestone: 7.2.4

comment:7 Changed 7 months ago by martinl

Still relevant?

Note: See TracTickets for help on using tickets.