Oolite hangs with 100% CPU use

[Miramor]

Not sure if this is the right place for this post, but I don't think it belongs in bugs because it's probably not an Oolite bug.

Anyway. I just tried installing the Ubuntu version of Oolite on Kubuntu 11.04. It started up (with the "Press space commander" screen) and when I pressed space displayed my ship's HUD... and there just hung, eating 80% of my CPU power and not responding to any keystroke (and not generating a log either). Okay, I thought, the Ubuntu version is probably bugged; I'll install the latest from the website.

So I installed the 1.75.1 autopackage version. Now all I get is the Oolite splash screen, which does not even refresh itself, and 100% CPU usage (with no hard drive activity at all, so I know it isn't loading what it ought to).

My log looks like this:

Code: Select all

08:52:01.143 [log.header]: Opening log for Oolite version 1.75.1 (x86-32 test release) under Linux at 2011-05-08 08:52:01 -0500.
2 processors detected.
Build options: spoken messages, mass/fuel pricing, JavaScript console support, OXP verifier, localization tools, debug GraphViz support, JavaScript profiling.

Note that the contents of the log file can be adjusted by editing logcontrol.plist.

08:52:01.331 [display.mode.list.native]: X11 native resolution detected: 1024 x 600
08:52:01.815 [joystick.init]: Number of joysticks detected: 0
08:52:01.823 [dataCache.notFound]: No data cache found, starting from scratch.
08:52:01.824 [searchPaths.dumpAll]: Unrestricted mode - resource paths:
    ~/.local/lib/Oolite/oolite.app/Resources
    AddOns
08:52:01.824 [rendering.opengl.version]: OpenGL renderer version: 1.4.0 ("1.4 Mesa 7.10.2"). Vendor: "Tungsten Graphics, Inc". Renderer: "Mesa DRI Intel(R) 945GME GEM 20100330 DEVELOPMENT x86/MMX/SSE2".
08:52:01.825 [rendering.opengl.extensions]: OpenGL extensions (108):
GL_EXT_abgr, GL_ARB_texture_env_crossbar, GL_EXT_texture, GL_ARB_shadow, GL_IBM_texture_mirrored_repeat, GL_EXT_texture_edge_clamp, GL_EXT_separate_specular_color, GL_EXT_blend_minmax, GL_EXT_texture_object, GL_ARB_texture_env_add, GL_INGR_blend_func_separate, GL_NV_texture_env_combine4, GL_EXT_texture_cube_map, GL_EXT_blend_logic_op, GL_ARB_draw_elements_base_vertex, GL_EXT_texture_env_dot3, GL_IBM_rasterpos_clip, GL_EXT_framebuffer_blit, GL_ARB_texture_env_dot3, GL_NV_light_max_exponent, GL_EXT_framebuffer_object, GL_EXT_blend_subtract, GL_EXT_copy_texture, GL_3DFX_texture_compression_FXT1, GL_EXT_separate_shader_objects, GL_MESA_window_pos, GL_ARB_multitexture, GL_EXT_stencil_wrap, GL_ARB_texture_border_clamp, GL_NV_vertex_program, GL_ARB_texture_env_combine, GL_EXT_framebuffer_multisample, GL_SGIS_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_packed_pixels, GL_SGIS_texture_lod, GL_ARB_depth_texture, GL_ARB_transpose_matrix, GL_NV_texgen_reflection, GL_NV_packed_depth_stencil, GL_EXT_stencil_two_side, GL_ARB_shading_language_100, GL_OES_EGL_image, GL_EXT_rescale_normal, GL_EXT_gpu_program_parameters, GL_ARB_map_buffer_range, GL_ARB_provoking_vertex, GL_ARB_pixel_buffer_object, GL_ARB_explicit_attrib_location, GL_EXT_secondary_color, GL_SUN_multi_draw_arrays, GL_OES_read_format, GL_ARB_texture_mirrored_repeat, GL_ARB_copy_buffer, GL_EXT_polygon_offset, GL_EXT_draw_range_elements, GL_EXT_blend_equation_separate, GL_ARB_half_float_pixel, GL_EXT_texture_lod_bias, GL_EXT_texture_filter_anisotropic, GL_SGIS_texture_border_clamp, GL_SGIS_generate_mipmap, GL_NV_texture_rectangle, GL_APPLE_object_purgeable, GL_ARB_texture_rectangle, GL_ARB_texture_non_power_of_two, GL_ARB_point_sprite, GL_EXT_packed_depth_stencil, GL_ARB_vertex_shader, GL_ARB_vertex_buffer_object, GL_ARB_sync, GL_ARB_shader_objects, GL_EXT_provoking_vertex, GL_IBM_multimode_draw_arrays, GL_MESA_ycbcr_texture, GL_ATI_separate_stencil, GL_EXT_texture_rectangle, GL_ARB_fragment_shader, GL_EXT_texture3D, GL_EXT_fog_coord, GL_EXT_subtexture, GL_ARB_window_pos, GL_EXT_point_parameters, GL_ARB_fragment_program, GL_EXT_texture_env_combine, GL_ARB_vertex_program, GL_EXT_compiled_vertex_array, GL_EXT_bgra, GL_ARB_texture_cube_map, GL_ARB_point_parameters, GL_EXT_vertex_array, GL_ARB_multisample, GL_APPLE_client_storage, GL_ARB_vertex_array_object, GL_ARB_draw_buffers, GL_EXT_multi_draw_arrays, GL_ARB_texture_compression, GL_APPLE_vertex_array_object, GL_ATI_texture_env_combine3, GL_APPLE_packed_pixels, GL_EXT_blend_func_separate, GL_MESA_pack_invert, GL_EXT_shadow_funcs, GL_ATI_blend_equation_separate, GL_EXT_blend_color, GL_NV_vertex_program1_1, GL_NV_blend_square, GL_EXT_pixel_buffer_object
08:52:01.845 [script.javaScript.willLoad]: About to load JavaScript /home/proteus/.local/lib/Oolite/oolite.app/Resources/Scripts/oolite-global-prefix.js
  08:52:01.851 [script.javaScript.load.success]: Loaded JavaScript: oolite-global-prefix 1.75.1 -- (no description)
08:52:01.853 [rendering.opengl.gpuSpecific]: Matched GPU configuration "Intel GMA 900/950 family".
08:52:01.854 [rendering.opengl.shader.support]: Shaders are supported.
08:52:02.043 [shipData.load.begin]: Loading ship data.
08:52:02.750 [script.javaScript.willLoad]: About to load JavaScript /home/proteus/.local/lib/Oolite/oolite.app/Resources/Scripts/oolite-default-player-script.js
  08:52:02.751 [script.javaScript.load.success]: Loaded JavaScript: oolite-default-player-script 1.75.1 -- Standard script for player ship.
08:52:02.763 [script.javaScript.willLoad]: About to load JavaScript /home/proteus/.local/lib/Oolite/oolite.app/Resources/Scripts/oolite-global-prefix.js
  08:52:02.765 [script.javaScript.load.success]: Loaded JavaScript: oolite-global-prefix 1.75.1 -- (no description)
08:52:02.767 [script.javaScript.willLoad]: About to load JavaScript /home/proteus/.local/lib/Oolite/oolite.app/Resources/Scripts/oolite-locale-functions.js
  08:52:02.774 [script.javaScript.load.success]: Loaded JavaScript: oolite-locale-functions 1.75.1 -- (no description)
08:52:02.775 [script.javaScript.willLoad]: About to load JavaScript /home/proteus/.local/lib/Oolite/oolite.app/Resources/Scripts/oolite-constrictor-hunt-mission.js
  08:52:02.778 [script.javaScript.load.success]: Loaded JavaScript: oolite-constrictor-hunt 1.75.1 -- (no description)
08:52:02.779 [script.javaScript.willLoad]: About to load JavaScript /home/proteus/.local/lib/Oolite/oolite.app/Resources/Scripts/oolite-cloaking-device-mission.js
  08:52:02.780 [script.javaScript.load.success]: Loaded JavaScript: oolite-cloaking-device 1.75.1 -- Cloaking device mission in galaxy 5.
08:52:02.781 [script.javaScript.willLoad]: About to load JavaScript /home/proteus/.local/lib/Oolite/oolite.app/Resources/Scripts/oolite-nova-mission.js
  08:52:02.786 [script.javaScript.load.success]: Loaded JavaScript: oolite-nova 1.75.1 -- (no description)
08:52:02.787 [script.javaScript.willLoad]: About to load JavaScript /home/proteus/.local/lib/Oolite/oolite.app/Resources/Scripts/oolite-thargoid-plans-mission.js
  08:52:02.789 [script.javaScript.load.success]: Loaded JavaScript: oolite-thargoid-plans 1.75.1 -- (no description)
08:52:02.789 [script.javaScript.willLoad]: About to load JavaScript /home/proteus/.local/lib/Oolite/oolite.app/Resources/Scripts/oolite-trumbles-mission.js
  08:52:02.791 [script.javaScript.load.success]: Loaded JavaScript: oolite-trumbles 1.75.1 -- Random offers of trumbles.
08:52:02.792 [script.load.world.listAll]: Loaded 5 world scripts:
    oolite-cloaking-device 1.75.1
    oolite-constrictor-hunt 1.75.1
    oolite-nova 1.75.1
    oolite-thargoid-plans 1.75.1
    oolite-trumbles 1.75.1
08:52:06.127 [script.javaScript.willLoad]: About to load JavaScript /home/proteus/.local/lib/Oolite/oolite.app/Resources/Scripts/oolite-default-ship-script.js
  08:52:06.129 [script.javaScript.load.success]: Loaded JavaScript: oolite-default-ship-script 1.75.1 -- Standard script for ships.

Oh, one other thing: I've overridden sync-to-vblank by exporting vblank_mode=0. This is kind of necessary on low-end Intel GPUs like mine; they don't have the power to handle sync-to-vblank, and will give awful FPS unless you disable it, even though it's the default for some reason. Believe me, tearing is not a problem on these GPUs.

So... yeah. What's going on? How can I fix it?

[Capt. Murphy]

Can't be sure but on my windows PC when I came back to Oolite recently it wouldn't run properly until I'd upgraded drivers for my graphics card. It did launch though just gave a consistent frame rate of about 3 frames per second.

From memory the drivers I had installed at the time had a OpenGL renderer version: 1.4.0 same as yours - I think the current Oolite releases really need an OpenGl renderer of 2.0 +.

Maybe a scoot around to see if you can find new drivers for your card?

[Miramor]

This being Ubuntu 11.04, I'm pretty sure these are the newest drivers...

[Cody]

I can't help with your problem Miramor, I'm just a pilot... welcome aboard though.

[Thargoid]

I wonder a little if you're waiting long enough. On my machine the first run (or when the cache is rebuilt) takes a lot of time and keeps the machine quite busy for about a minute (and this is a new 4GB I5 laptop). Win7 identifies Oolite as not responding, but if you wait for a bit then things come to life again and we get underway.

How long are you leaving things?

[Miramor]

About 30 seconds...

[Thargoid]

Mine sometimes takes longer than that, up to a few minutes if it's a full cache rebuild.

Try it again, start with shift held down and then give it a few minutes and see if the game does start. Once the cache is built then things get a lot quicker.

[Lone_Wolf]

Miramor , check out my thread [LINUX] ATI Radeon 2xxx and higher problems .

The intel OSS drivers also use the mesa gallium drivers, and atleast 1 archlinux user with intel graphics had exactly the same problems as i had with ATI radeon.

[Capt. Murphy]

@ Thargoid

I'm quite shocked at your timings - I just timed launch on my machine - I've got it set to always rebuild the cache and is loading about 30 OXP's - I get about 12 seconds to spinning cobra. That's on a 6 year old XP laptop with a 1.73 Ghz Celeron processor and 1GB of RAM.

The one thing I do have on my machine is an aggressive daily defrag using a 3rd party defragmenter which I've customised to facilitate quick application launch in general.

@ Miramor - give the new release 1.75.2 a go.

[Eric Walch]

@ Thargoid

I'm quite shocked at your timings - I just timed launch on my machine - I've got it set to always rebuild the cache and is loading about 30 OXP's - I get about 12 seconds to spinning cobra. That's on a 6 year old XP laptop with a 1.73 Ghz Celeron processor and 1GB of RAM.

Thargoid once said that he is running Oolite from his memory stick. So he is probably testing the speed of his stick and not his computer

[Thargoid]

Yup there is that element to it as well...

I run the thing on so many computers these days (three or four at home plus my work laptop where I couldn't "officially" have it installed anyway) that doing it from stick is the only way not to end up with too many different versions and iterations of OXPs and trunk installs.