Getting crashes always ending with bigships report
Moderators: winston, another_commander
- Lestradae
- ---- E L I T E ----
- Posts: 3095
- Joined: Tue Apr 17, 2007 10:30 pm
- Location: Vienna, Austria
Getting crashes always ending with bigships report
Last crash, end of crash log:
[/quote]22:23:51.013 [CargoTypeExtension]: Set price for CTE_CTD_12 to 68 with 0 TC available
22:23:51.013 [CargoTypeExtension]: Set price for CTE_CTD_13 to 11 with 0 TC available
22:23:51.013 [CargoTypeExtension]: Set price for CTE_CTD_14 to 37 with 0 TC available
22:23:51.013 [CargoTypeExtension]: Set price for CTE_CTD_15 to 65 with 0 TC available
22:23:51.013 [CargoTypeExtension]: Set price for CTE_CTD_16 to 6 with 0 TC available
22:23:51.014 [CargoTypeExtension]: Set price for CTE_CTD_17 to 24 with 0 TC available
22:23:51.014 [CargoTypeExtension]: Set price for CTE_CTD_18 to 68 with 0 TC available
22:23:51.014 [CargoTypeExtension]: Set price for CTE_CTD_19 to 16 with 0 TC available
22:23:51.014 [CargoTypeExtension]: Set price for CTE_CTD_20 to 59 with 0 TC available
22:23:51.014 [testscript.spawn]: Generated 1 nest for testing purposes.
22:23:51.083 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/jorg2_e.png
22:23:51.083 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/jorg2.png
22:23:51.084 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/jorg2_n.png
22:23:51.191 [general.error.allocationFailure]: Failed to allocate space (1800000 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/obey.png
22:23:51.239 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/bh01.png
22:23:51.240 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/bh01_e.png
22:23:51.240 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/bh01_n.png
22:23:51.241 [bigShips_populator]: 1 big trader(s) added to the Ceinerxe system.[/quote]
Had a CTD four times in a row now while testing the WiP Wormhole generator (Jump-optimised). First thought it had to do with that. Then I noticed that every time the crash left a "X big trader(s) added to the XXX system." in the log. Never a "0 big trader(s)" which it also writes down I think, and always this.
Perhaps for someone the info is useful as to what is going on.
[/quote]22:23:51.013 [CargoTypeExtension]: Set price for CTE_CTD_12 to 68 with 0 TC available
22:23:51.013 [CargoTypeExtension]: Set price for CTE_CTD_13 to 11 with 0 TC available
22:23:51.013 [CargoTypeExtension]: Set price for CTE_CTD_14 to 37 with 0 TC available
22:23:51.013 [CargoTypeExtension]: Set price for CTE_CTD_15 to 65 with 0 TC available
22:23:51.013 [CargoTypeExtension]: Set price for CTE_CTD_16 to 6 with 0 TC available
22:23:51.014 [CargoTypeExtension]: Set price for CTE_CTD_17 to 24 with 0 TC available
22:23:51.014 [CargoTypeExtension]: Set price for CTE_CTD_18 to 68 with 0 TC available
22:23:51.014 [CargoTypeExtension]: Set price for CTE_CTD_19 to 16 with 0 TC available
22:23:51.014 [CargoTypeExtension]: Set price for CTE_CTD_20 to 59 with 0 TC available
22:23:51.014 [testscript.spawn]: Generated 1 nest for testing purposes.
22:23:51.083 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/jorg2_e.png
22:23:51.083 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/jorg2.png
22:23:51.084 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/jorg2_n.png
22:23:51.191 [general.error.allocationFailure]: Failed to allocate space (1800000 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/obey.png
22:23:51.239 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/bh01.png
22:23:51.240 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/bh01_e.png
22:23:51.240 [general.error.allocationFailure]: Failed to allocate space (4194304 bytes) for texture ../AddOns/adcks_bulk_haulers_v1.4.oxp/Textures/bh01_n.png
22:23:51.241 [bigShips_populator]: 1 big trader(s) added to the Ceinerxe system.[/quote]
Had a CTD four times in a row now while testing the WiP Wormhole generator (Jump-optimised). First thought it had to do with that. Then I noticed that every time the crash left a "X big trader(s) added to the XXX system." in the log. Never a "0 big trader(s)" which it also writes down I think, and always this.
Perhaps for someone the info is useful as to what is going on.
- Lestradae
- ---- E L I T E ----
- Posts: 3095
- Joined: Tue Apr 17, 2007 10:30 pm
- Location: Vienna, Austria
Re: Getting crashes always ending with bigships report
Ah, perhaps:
... also relevant.22:19:49.204 [log.header]: Opening log for Oolite version 1.76 (x86-32 test release) under Windows at 2012-02-25 22:19:49 +0100.
4 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.
22:19:49.503 [display.mode.list.native]: Windows native resolution detected: 1920 x 1080
22:19:49.868 [joystick.init]: Number of joysticks detected: 0
22:19:50.914 [searchPaths.dumpAll]: Unrestricted mode - resource paths:
Resources
../AddOns
../AddOns/a-wing.oxp
../AddOns/AAACrooks.oxp
../AddOns/Accipiter.oxp
../AddOns/Ace-ships_CruzerV0.9.4.oxp
../AddOns/Ace-ships_HornetV0.9.2.oxp
../AddOns/Ace-ships_night-adderV0.9.1.oxp
../AddOns/ACS_1.2.oxp
../AddOns/adcks_bulk_haulers_v1.4.oxp
../AddOns/adcks_eagles_v1.1.oxp
../AddOns/adck_gold_cobra.oxp
../AddOns/aegidian-special.oxp
../AddOns/Anarchies2.6.oxp
../AddOns/aphidv2.oxp
../AddOns/Aquatics 2.27.oxp
../AddOns/Armoury 1.09.oxp
../AddOns/Assassins.oxp
../AddOns/AsteroidStorm 4.02.oxp
../AddOns/att1.oxp
../AddOns/Auto-ECM 0.2.oxp
../AddOns/AutoSkim.oxp
../AddOns/auto_eject.oxp
../AddOns/b-wing.oxp
../AddOns/Baakili_Far_Trader_v2.0.oxp
../AddOns/bandersnatch.oxp
../AddOns/Basic-debug.oxp
../AddOns/BeerCooler1.0.1.oxp
../AddOns/behemoth 2.6.oxp
../AddOns/BehemothSpacewar 1.2.3.oxp
../AddOns/BGS-A1.4.oxp
../AddOns/BigShips 1.02.oxp
../AddOns/BlackCobrawithC4HUD.oxp
../AddOns/black_baron.oxp
../AddOns/BlOombergMarkets v2.5.oxp
../AddOns/boomslang.oxp
../AddOns/BountyScannerv2.0.oxp
../AddOns/BountyStatus 1.00.oxp
../AddOns/boyracers.oxp
../AddOns/Breakable_HUD_IFF_Scanner.oxp
../AddOns/Breakable_Shield_Generators.oxp
../AddOns/Breakable_TorusDrive.oxp
../AddOns/Breakable_WitchDrive.oxp
../AddOns/BuoyRepair1.3.1.oxp
../AddOns/Cabal_Common_Library1.5.oxp
../AddOns/captKev_dodo.oxp
../AddOns/CargoShepherd1.01.oxp
../AddOns/Cargo_wrecks_teaser 1.7.oxp
../AddOns/ChupacabraV1.1.oxp
../AddOns/ClippersV1.2.oxp
../AddOns/CloakRepair.oxp
../AddOns/cobra35.oxp
../AddOns/cobra3njx.oxp
../AddOns/Cobra3XT.oxp
../AddOns/cobraClipper 1.1.1.oxp
../AddOns/Coluber_0_6_0_2011-12-17.oxp
../AddOns/Commies.oxp
../AddOns/Condorv1.1.oxp
../AddOns/contractorMkII.oxp
../AddOns/Copperheadv0.75.oxp
../AddOns/CopperheadYari.oxp
../AddOns/Coyote'sRun.oxp
../AddOns/Coyote'sRunForGriff.oxp
../AddOns/Dark_Rainbow.oxp
../AddOns/DeepSpacePirates 1.3.oxp
../AddOns/DeepspaceShip.oxp
../AddOns/Deep_Horizon_Nav_Buoy.oxp
../AddOns/Delightful-Docking.oxp
../AddOns/Deposed1.3.4.oxp
../AddOns/Diamondback.oxp
../AddOns/Dictators v1.5.oxp
../AddOns/Diso.oxp
../AddOns/display_reputation.oxp
../AddOns/DockingClearance.oxp
../AddOns/dragon.oxp
../AddOns/DragonfireflystV1.2.oxp
../AddOns/Dredgers2.4.6.oxp
../AddOns/dwcobra3.oxp
../AddOns/eagle2.oxp
../AddOns/Energy Equipment 1.11.oxp
../AddOns/EnhancedMisjump_1.1.oxp
../AddOns/Escape_Capsule_Locator_1.4_2011-12-18.oxp
../AddOns/Escort_Contracts_1.5.1_2012-02-05.oxp
../AddOns/ettBeaconLauncher1.02.oxp
../AddOns/Executive Spacewaysv2.4.oxp
../AddOns/Explorers'_Club_1.3.1_2012-01-21.oxp
../AddOns/Extra Thargoids.oxp
../AddOns/ExtraFuelTanksV1.3.oxp
../AddOns/Factions-1.10.oxp
../AddOns/Famous_Planets_v2.5.oxp
../AddOns/FarstarMurderer1.1.oxp
../AddOns/Far_Arm_ships_v2.0.oxp
../AddOns/ferdelance_3G.oxp
../AddOns/ferdelance_ng.oxp
../AddOns/Ferdepai.oxp
../AddOns/Firebirdv1.2.oxp
../AddOns/Firewasp.oxp
../AddOns/fireworks.oxp
../AddOns/FlightLog1.03.oxp
../AddOns/flying_Dutchman.oxp
../AddOns/FP Liners 1.00.oxp
../AddOns/fsr.oxp
../AddOns/FTZ v0.15.oxp
../AddOns/FuelCollectorV0.07.oxp
../AddOns/FuelStation1.34.oxp
../AddOns/FuelTankv2.2.oxp
../AddOns/Furball-1.5.oxp
../AddOns/Galactic_Navy 5.4.3.oxp
../AddOns/GalaxyInfo.oxp
../AddOns/Galcop_trade_outpost.oxp
../AddOns/GalDrive Programmers.oxp
../AddOns/GalDrivePodv1.3.oxp
../AddOns/Gates1.13.oxp
../AddOns/Generation Ships.oxp
../AddOns/genericHUD.oxp
../AddOns/Genesisv1.0.oxp
../AddOns/globestation2.0.oxp
../AddOns/Graffiti_starter_pack.oxp
../AddOns/greekshipset1.oxp
../AddOns/GreenGeckov1.0SA.oxp
../AddOns/griffin2.oxp
../AddOns/griff_boa_prototype_normalmapped.oxp
../AddOns/Griff_Debris_Core_Ships.oxp
../AddOns/Griff_Debris_sets135_no_normal_map.oxp
../AddOns/griff_halloween_witch_v1.5.oxp
../AddOns/Griff_illicit_unlock.oxp
../AddOns/griff_krait_v1.1.oxp
../AddOns/Griff_Shipset_Addition_v1.0.oxp
../AddOns/Griff_Shipset_Resources_v1.2.22.oxp
../AddOns/GrittyCoriolis.oxp
../AddOns/gwxstations.oxp
../AddOns/haulerp30V1.3.oxp
../AddOns/Herald.oxp
../AddOns/HiredGuns1.26.oxp
../AddOns/hOopyCasino1.2.oxp
../AddOns/Hotrods.oxp
../AddOns/HyperCargo1.04.oxp
../AddOns/Hyperradio1.24.oxp
../AddOns/I-Missile.oxp
../AddOns/icarus.oxp
../AddOns/Ice-asteroidsV2.1.oxp
../AddOns/Illegal_goods_tweak_1.6_2012.02.05.oxp
../AddOns/illicit_unlock_FIX1.56.oxp
../AddOns/impcourier2.oxp
../AddOns/imptrader.oxp
../AddOns/Interceptor.oxp
../AddOns/InterstellarTweaksCrashesPossible.oxp
../AddOns/interstellar_help.oxp
../AddOns/ionics-1.3.1.oxp
../AddOns/IronHide 2.00.oxp
../AddOns/Iron_Raven_v1.1.oxp
../AddOns/Isisinterstellar.oxp
../AddOns/ixianfreighter.oxp
../AddOns/ixianships1.2.oxp
../AddOns/jabberwocky.oxp
../AddOns/Kestrel&Falcon.oxp
../AddOns/kestros-mk4-beta1.oxp
../AddOns/Killit.oxp
../AddOns/KingCobra.oxp
../AddOns/kirin.oxp
../AddOns/KonekoKobra_1.0.0.oxp
../AddOns/lambda.oxp
../AddOns/lane_legal.oxp
../AddOns/Lave Academy 1.31.oxp
../AddOns/Lave.oxp
../AddOns/liners_v1.2.oxp
../AddOns/LinkG7v0.1.oxp
../AddOns/Llama.oxp
../AddOns/LongRangeScanner v0.2.oxp
../AddOns/longshot.oxp
../AddOns/longway 1.1.oxp
../AddOns/lovecats 1.3.0.oxp
../AddOns/Manta.oxp
../AddOns/Marauder1.0.oxp
../AddOns/marett_vol1.oxp
../AddOns/Merlin.oxp
../AddOns/MFLPS.oxp
../AddOns/MilHUD-new.oxp
../AddOns/militaryFiasco2.5.2.oxp
../AddOns/MilitaryFuelInjectors 1.00.oxp
../AddOns/milmissile.oxp
../AddOns/MisjumpAnalyser1.1.oxp
../AddOns/MisjumpInducerv0.2.oxp
../AddOns/MissileAnalyser1.2.oxp
../AddOns/MissilesandBombsv2.5.oxp
../AddOns/missile_spoof.oxp
../AddOns/Missionaries.oxp
../AddOns/Moccasin.oxp
../AddOns/monument.oxp
../AddOns/morrigan.oxp
../AddOns/mPakRedux.oxp
../AddOns/multidecal_cobraIII_player.oxp
../AddOns/murgh_Xships1.0.1.oxp
../AddOns/NavalGrid1.00.oxp
../AddOns/NavalTorpedo.oxp
../AddOns/NavalTorpedo.oxp/Naval Torpedo.oxp
../AddOns/Neolite_Core_Addition_1.1.oxp
../AddOns/Neolite_Core_Resources_A_1.1.oxp
../AddOns/Neolite_Core_Resources_B_1.1.oxp
../AddOns/newships.oxp
../AddOns/New_Cargoes_0.4.0.oxp
../AddOns/Nexusmissile.oxp
../AddOns/NovaBat_Redux.oxp
../AddOns/NPC-shields.oxp
../AddOns/Nuit.oxp
../AddOns/nukes0.98.oxp
../AddOns/nuvipers.oxp
../AddOns/offender_traders.oxp
../AddOns/Oo-Haul.oxp
../AddOns/OresratiChalenge v0.9.oxp
../AddOns/Ore_processor1.59.oxp
../AddOns/Orisisv1.3.oxp
../AddOns/outrider.oxp
../AddOns/pagroove_Aurorav1.1.oxp
../AddOns/PAG_oldships_v2.5.oxp
../AddOns/Pallas2.0.2.oxp
../AddOns/pelamis.oxp
../AddOns/phoenix.oxp
../AddOns/piratetraps.oxp
../AddOns/Pirate_coves1.3.2.oxp
../AddOns/PlanetFall 1.41.oxp
../AddOns/PlanetFall Link - Black Monks 1.0.oxp
../AddOns/PlanetFall Link - hOopy Casino 1.0.oxp
../AddOns/PlanetFall Mission - Oo-Haul 1.11.oxp
../AddOns/PlanetFall Mission - Taxi 1.11.oxp
../AddOns/Pods 1.22.oxp
../AddOns/Pods-UPS 1.22.oxp
../AddOns/Police_Scanner_Upgrade_1.3.1_2011-12-18.oxp
../AddOns/PrimableLaser.oxp
../AddOns/PTI.oxp
../AddOns/PylonBasedEqRemoverv0.8.oxp
../AddOns/Q-Chargerv1.2.oxp
../AddOns/racers.oxp
../AddOns/railgun.oxp
../AddOns/ramon_anaconda.oxp
../AddOns/RandomHits1.4.12.oxp
../AddOns/randomshipnames.oxp
../AddOns/Reduxed.oxp
../AddOns/renegades.oxp
../AddOns/RepairBots 2.04.oxp
../AddOns/Rescue_Stations_1.2.2.oxp
../AddOns/ResistanceCommander_v1.3.oxp
../AddOns/RetroRockets1.00.oxp
../AddOns/ringpod1.1.2.oxp
../AddOns/RingRacer1.21.oxp
../AddOns/RoC2.1.oxp
../AddOns/Rock_Hermit_Locator1.3.3.oxp
../AddOns/RVandGS1.1.oxp
../AddOns/s-ships1.oxp
../AddOns/Salezav2.3.oxp
../AddOns/santa1.2.oxp
../AddOns/SaveAnywhere3.2.oxp
../AddOns/Scimitar.oxp
../AddOns/scorpius.oxp
../AddOns/SecondWave1.34.oxp
../AddOns/sell_equipment.oxp
../AddOns/SensibleBeacons1.0.oxp
../AddOns/SensibleLasers.oxp
../AddOns/seosu.oxp
../AddOns/Shady_blackmonks.oxp
../AddOns/shady_sungs.oxp
../AddOns/Shield-tail.oxp
../AddOns/ShieldEqualizer+Capacitorsv1.3.oxp
../AddOns/Shrike.oxp
../AddOns/Shuriken.oxp
../AddOns/SIRF20.oxp
../AddOns/Smivs'Shipset-v4-HD-add.oxp
../AddOns/Snapper.oxp
../AddOns/snark.oxp
../AddOns/SniperCameraSystemv1.1.oxp
../AddOns/SniperLockv1.oxp
../AddOns/Snoopers2.2.1.oxp
../AddOns/Sothis.oxp
../AddOns/spearhead_1.0.1_2011-11-15.oxp
../AddOns/Spectre.oxp
../AddOns/spyhunter 1.1.oxp
../AddOns/Staer9scout.oxp
../AddOns/Staer9spectre.oxp
../AddOns/staer9xeikilmk2V1.1.oxp
../AddOns/Staer9xeikilV2.oxp
../AddOns/staer9_chopped_cobraV1.1.1.oxp
../AddOns/Staer9_fireflyV0.5.oxp
../AddOns/Staer9_GHOST_gunshipV1.2.oxp
../AddOns/Staer9_GHOST_raptorV0.9.1.oxp
../AddOns/star-jelly_v1.1.oxp
../AddOns/Status_Quo_Q-bomb.oxp
../AddOns/Stealth1.04.oxp
../AddOns/StellarSerpents 1.21.oxp
../AddOns/Stingray.oxp
../AddOns/Submersible_Nebulae.oxp
../AddOns/SunBat-redux.oxp
../AddOns/SunBatMkIIv1.3.oxp
../AddOns/sunskimmers.oxp
../AddOns/supercobra1.4.2.oxp
../AddOns/Superhubv1.2.oxp
../AddOns/Swarm1.03.oxp
../AddOns/Swift.oxp
../AddOns/System_Redux.oxp
../AddOns/TAF_reset.oxp
../AddOns/TalkativeCompass_1.0.3.oxp
../AddOns/Taranis1.2.oxp
../AddOns/TargetAutolockPlus1.12.oxp
../AddOns/TargetRange-1.0a1.oxp
../AddOns/TargetReticle1.2.1.oxp
../AddOns/Taxi_Galactica.oxp
../AddOns/TCAT1.10.oxp
../AddOns/terrapin.oxp
../AddOns/tesoura.oxp
../AddOns/TG2-Griff(all-in)_apocalypse.oxp
../AddOns/TG2forSmivs' Apocalypse.oxp
../AddOns/thargoidcarrier.oxp
../AddOns/thargoid_wars 4.5.4.oxp
../AddOns/Thargorn_Threat 1.5.oxp
../AddOns/The_Feudal_States_v1.13.oxp
../AddOns/Tianve1.3.oxp
../AddOns/TIE.oxp
../AddOns/tiger.oxp
../AddOns/TionislaReporter1.0.oxp
../AddOns/TOGY_Main 1.1.oxp
../AddOns/TOGY_Monuments pack.oxp
../AddOns/Tori2.01.oxp
../AddOns/total_patrol.oxp
../AddOns/ToughGuysApocalypse.oxp
../AddOns/TrafficControl1.11.oxp
../AddOns/transhab.oxp
../AddOns/Transports2.52.oxp
../AddOns/Trident Downv2.2.oxp
../AddOns/tugs.oxp
../AddOns/TurboAnaconda.oxp
../AddOns/UPS-courierv1.7.8.oxp
../AddOns/UrutuMKIII.oxp
../AddOns/urutu_IV.oxp
../AddOns/Vamp3a.oxp
../AddOns/Vector1.6.oxp
../AddOns/velocity.oxp
../AddOns/vendetta.oxp
../AddOns/Venom.oxp
../AddOns/Victim11_1.0.oxp
../AddOns/Vortex1.22.oxp
../AddOns/Wasps.oxp
../AddOns/weeviloid2.oxp
../AddOns/WelcomeMat1.11.oxp
../AddOns/werewolf.oxp
../AddOns/wolfmk2.oxp
../AddOns/wolfwoods_variants.oxp
../AddOns/WonderWormV1.2.oxp
../AddOns/WormholeDronesWIP.oxp
../AddOns/wormhole_restoration.oxp
../AddOns/WPB1.1.oxp
../AddOns/X-Wing.oxp
../AddOns/xarik.oxp
../AddOns/XeptatlsSwordv1.0.2.oxp
../AddOns/y-wing.oxp
../AddOns/YellOoCabsV2.0.oxp
../AddOns/YOUR_AD_HERE.oxp
../AddOns/YOUR_AD_HERE_set_A.oxp
../AddOns/YOUR_AD_HERE_set_A417_upd.oxp
../AddOns/YOUR_AD_HERE_set_B.oxp
../AddOns/YOUR_AD_HERE_set_B417_upd.oxp
../AddOns/YOUR_AD_HERE_set_C.oxp
../AddOns/YOUR_AD_HERE_set_C417_upd.oxp
../AddOns/YOUR_AD_HERE_set_D.oxp
../AddOns/YOUR_AD_HERE_set_D417_upd.oxp
../AddOns/YOUR_AD_HERE_set_E.oxp
../AddOns/YOUR_AD_HERE_set_E417_upd.oxp
../AddOns/YOUR_AD_HERE_set_F.oxp
../AddOns/YOUR_AD_HERE_set_F417_upd.oxp
../AddOns/YOUR_AD_HERE_set_G.oxp
../AddOns/YOUR_AD_HERE_Z.oxp
../AddOns/Z-ships_v1.0.oxp
../AddOns/ZZZZ-MyKeyboardSettings.oxp
../AddOns/Z_GrOovy_Cobra_AC.oxp
../AddOns/Z_GrOovy_System_Stations.oxp
../AddOns/Z_GrOovy_Viper_Raider.oxp
../AddOns/Z_GrOovy_YAH_Player_Sidewinder_Variety_Pack.oxp
../AddOns/Z_GrOovy_YAH_Sidewinder_Variety_Pack.oxp
../AddOns/Z_GrOovy_YellOo_Cab_Variety_Pack.oxp
- Cody
- Sharp Shooter Spam Assassin
- Posts: 16081
- Joined: Sat Jul 04, 2009 9:31 pm
- Location: The Lizard's Claw
- Contact:
Re: Getting crashes always ending with bigships report
<chuckles>Lestradae wrote:Ah, perhaps: [snip]... also relevant.
I would advise stilts for the quagmires, and camels for the snowy hills
And any survivors, their debts I will certainly pay. There's always a way!
And any survivors, their debts I will certainly pay. There's always a way!
- Lestradae
- ---- E L I T E ----
- Posts: 3095
- Joined: Tue Apr 17, 2007 10:30 pm
- Location: Vienna, Austria
Re: Getting crashes always ending with bigships report
Are there any oxps that have bigships inbuilt, could something like that cause a CTD, if the same script ran twice?
Re: Getting crashes always ending with bigships report
bigShips is just a populator script (using a specific role of "bigTrader"). There are numerous OXPs with such populators using various roles, used to add any ship or station without a "generic" type role (as used by the built-in populator).
But I would doubt bigShips itself can cause the problem directly. From your log you're getting failures to allocate memory, so it may be that you are low. Then adding any kind of large or complicatedly drawn ship (such as those which bigShips will, but also many others) could cause your machine to hit the ceiling memory-wise and have problems.
But I would doubt bigShips itself can cause the problem directly. From your log you're getting failures to allocate memory, so it may be that you are low. Then adding any kind of large or complicatedly drawn ship (such as those which bigShips will, but also many others) could cause your machine to hit the ceiling memory-wise and have problems.
My OXPs via Boxspace or from my Wiki pages .
Thargoid TV
Dropbox Referral Link
Thargoid TV
Dropbox Referral Link
- Eric Walch
- Slightly Grand Rear Admiral
- Posts: 5536
- Joined: Sat Jun 16, 2007 3:48 pm
- Location: Netherlands
Re: Getting crashes always ending with bigships report
Don't focus to much on bigShips as it always will do a log on populating a new system. This is the moment that a lot of other oxps also are adding ships. BigShips prefers systems with a higher economic level, so it might be another oxp that adds ships to such systems.
And, as thargoid writes, you are also low on memory because some textures could not be loaded. Maybe its now a more essential thing that is not loaded.?
And, as thargoid writes, you are also low on memory because some textures could not be loaded. Maybe its now a more essential thing that is not loaded.?
UPS-Courier & DeepSpacePirates & others at the box and some older versions
- Lestradae
- ---- E L I T E ----
- Posts: 3095
- Joined: Tue Apr 17, 2007 10:30 pm
- Location: Vienna, Austria
Re: Getting crashes always ending with bigships report
Correct of course, the bigships message simply coincides with whatever is loaded at the start of a new system - d'oh. OK so then not bigships.Eric Walch wrote:Don't focus to much on bigShips as it always ... you are also low on memory because some textures could not be loaded. Maybe its now a more essential thing that is not loaded.?
Strange thing is, I've had these out-of-memory crashes since I started to play oolite 5 years ago. OK, I am always the one who, oxp-wise, puts in everything and the kitchen sink on top, but that still doesn't explain to me why it can still happen to the much more stable 1.76 Oolite on my 16GB RAM, 3GHz quad-core, good graphic card machine ...
Edit: Windows 7 seems a possible culprit, too. Switched off the DEP (Data Exclusion Prevention) for Oolite, played it as an administrator, and did use the exe directly, not via desktop shortcut - no crashes oO
- Commander McLane
- ---- E L I T E ----
- Posts: 9520
- Joined: Thu Dec 14, 2006 9:08 am
- Location: a Hacker Outpost in a moderately remote area
- Contact:
Re: Getting crashes always ending with bigships report
It doesn't have to do with the stability of 1.76. If I understand correctly, it's the memory of your GPU you're running out of (texture memory). This is most likely the result of having many objects with big textures in your system. So there's a direct correlation to the number of OXPs: the more variety in ships, the more different textures are used.Lestradae wrote:OK, I am always the one who, oxp-wise, puts in everything and the kitchen sink on top, but that still doesn't explain to me why it can still happen to the much more stable 1.76 Oolite on my 16GB RAM, 3GHz quad-core, good graphic card machine ...
I don't know, though, why running out of texture memory leads to a crash. The Windows wizards may know.
-
- Quite Grand Sub-Admiral
- Posts: 6683
- Joined: Wed Feb 28, 2007 7:54 am
Re: Getting crashes always ending with bigships report
You have so many OXPs that you are physically hitting memory limits on your machine (video or RAM), especially since some of them include very big textures. Nothing unexpected really. Why it crashes? Well, for the same reason that any app hitting physical limits on memory has a very good chance of being stopped by Windows. Check if there is anything inside stderr.txt following a crash.Lestradae wrote:Strange thing is, I've had these out-of-memory crashes since I started to play oolite 5 years ago. OK, I am always the one who, oxp-wise, puts in everything and the kitchen sink on top, but that still doesn't explain to me why it can still happen to the much more stable 1.76 Oolite on my 16GB RAM, 3GHz quad-core, good graphic card machine ...
Shortcut or direct click on the exe has nothing to do with the crashes. It is essentially the same thing.Edit: Windows 7 seems a possible culprit, too. Switched off the DEP (Data Exclusion Prevention) for Oolite, played it as an administrator, and did use the exe directly, not via desktop shortcut - no crashes oO
Re: Getting crashes always ending with bigships report
I also had crashes coinciding with bigships popular logs using Windows 7. I changed all ships using the big trader role into the normal trader role and they populate normally and with no issues. I have a high performance computer so memory issues should not be a concern for me.
- Lestradae
- ---- E L I T E ----
- Posts: 3095
- Joined: Tue Apr 17, 2007 10:30 pm
- Location: Vienna, Austria
Re: Getting crashes always ending with bigships report
Interesting idea, will try that one out.Solonar wrote:I also had crashes coinciding with bigships popular logs using Windows 7. I changed all ships using the big trader role into the normal trader role and they populate normally and with no issues. I have a high performance computer so memory issues should not be a concern for me.
Though it is obviously correct that it could just be that the bigships message coincides with whatever else goes wrong at the startup to a new system. And I am getting the crashes only at the startup to a new system after a jump.
Had two further crashes - but played quite some time before and between those - and there was some windows message about running out of virtual memory. Because I can (my computer has that kind of space) I set the virtual memory threshold to a terabyte
The second crash did still happen, and I sincerely doubt that Oolite overran a terabyte data
I'll write should I find out about something new, but will try to replace the bigtrader role with trader in the meantime ...
Re: Getting crashes always ending with bigships report
If you change the role, expect to start seeing log errors about cancelled launches when the system tries to launch a big ship out of the standard sized letterbox of a station.
My OXPs via Boxspace or from my Wiki pages .
Thargoid TV
Dropbox Referral Link
Thargoid TV
Dropbox Referral Link
- Lestradae
- ---- E L I T E ----
- Posts: 3095
- Joined: Tue Apr 17, 2007 10:30 pm
- Location: Vienna, Austria
Re: Getting crashes always ending with bigships report
I should know about that So I won't try this, too.Thargoid wrote:If you change the role, expect to start seeing log errors about cancelled launches when the system tries to launch a big ship out of the standard sized letterbox of a station.
Re: Getting crashes always ending with bigships report
Thargoid wrote:If you change the role, expect to start seeing log errors about cancelled launches when the system tries to launch a big ship out of the standard sized letterbox of a station.
Yes I have seen these log errors but it does not negatively impact the Oolite performance as far as I can see. I changed the role to trader(0.1) so that their appearance are still semi-rare.
- Capt. Murphy
- Commodore
- Posts: 1127
- Joined: Fri Feb 25, 2011 8:46 am
- Location: UK South Coast.
Re: Getting crashes always ending with bigships report
As a possibly relevant or not observation I think Win 7s memory management may be a bit 'dodgy' in some way, particularly if it's coupled with a GPU that either exclusively uses system memory, or can borrow system memory in the event that it runs out of it's own.
1.76 is solid as a rock (as where all the 1.75.x) in terms of unexplained crashes on my old Win XP machine with an aging ATI card. The only unresolved problem was that it would consistently freeze during play, but only under Full Shaders. Everything was sweet as under Simple Shaders.
With my current machine (Win 7, Intel HD 3000 GPU) 6 GB RAM - the GPU can use up to 1.6GB of it - I've found a lot of variation in stability with different Graphics Drivers, with the newest ones being the worst for sudden crashes mid flight for no obvious reason. Stability can also be directly related to the Graphics Settings on the GPU control panel. If they are set to the highest level crashes are frequent, less so on the lower levels. Likelihood of crashing seems to be related to how much memory is being consumed.
One reasonably reproducible way (but not 100% - maybe about 25% with the most stable driver I could find) I can get the machine to crash, particularly if it's got a full load of OXP's is to switch the shader setting to No Shaders - Oolite resets the Graphics Engine in doing this, which I expect would involve unloading and reloading everything to the GPUs memory and a debug build of 1.76 revealed that it's a GPU driver file that's involved with this crash. So the conclusion I draw is that a lot of unreproducible crashes are Graphic Driver related, rather than Oolite related as such.
1.76 is solid as a rock (as where all the 1.75.x) in terms of unexplained crashes on my old Win XP machine with an aging ATI card. The only unresolved problem was that it would consistently freeze during play, but only under Full Shaders. Everything was sweet as under Simple Shaders.
With my current machine (Win 7, Intel HD 3000 GPU) 6 GB RAM - the GPU can use up to 1.6GB of it - I've found a lot of variation in stability with different Graphics Drivers, with the newest ones being the worst for sudden crashes mid flight for no obvious reason. Stability can also be directly related to the Graphics Settings on the GPU control panel. If they are set to the highest level crashes are frequent, less so on the lower levels. Likelihood of crashing seems to be related to how much memory is being consumed.
One reasonably reproducible way (but not 100% - maybe about 25% with the most stable driver I could find) I can get the machine to crash, particularly if it's got a full load of OXP's is to switch the shader setting to No Shaders - Oolite resets the Graphics Engine in doing this, which I expect would involve unloading and reloading everything to the GPUs memory and a debug build of 1.76 revealed that it's a GPU driver file that's involved with this crash. So the conclusion I draw is that a lot of unreproducible crashes are Graphic Driver related, rather than Oolite related as such.
Capt. Murphy's OXPs
External JavaScript resources - W3Schools & Mozilla Developer Network
Win 7 64bit, Intel Core i5 with HD3000 (driver rev. 8.15.10.2696 - March 2012), Oolite 1.76.1
External JavaScript resources - W3Schools & Mozilla Developer Network
Win 7 64bit, Intel Core i5 with HD3000 (driver rev. 8.15.10.2696 - March 2012), Oolite 1.76.1