Develop
Ticket #1460 (assigned defect)
Launch failure v6.2 HX4700 with US_MICHIGAN.xcm map
| Reported by: | therzog | Owned by: | minad |
|---|---|---|---|
| Priority: | normal | Milestone: | # Map Generator |
| Component: | Map | Version: | 6.0 |
| Keywords: | Cc: |
Description (last modified by apf) (diff)
-->> Device
iPaq HX4700
Win Mobile 2003
xcsoar v6.2
-->> Steps to duplicate
- DEL xcsoar-registry-.prf
- Launch xcsoar then QUIT (to create a Default registry)
- Restart xcsoar (sim)
- CONFIG -> CONFIG -> SYSTEM SETTINGS
- 1.Site Settings Add Map Database = US_MICHIGAN.xcm
- CLOSE (exit config screen)
- xcsoar appears to restart (load maps?) but returns to the iPaq Home menu screen
- Any attempt to launch xcsoar (sim) shows ...Initializing..Loading Terrain File.. Then exits (no error messages displayed)
-->> Notes:
- US_COLORADO.xcm loads OK
- Thinking US_MICHIGAN.xcm is corrupt, I downloaded a fresh copy. Still fails.
- US_MICHIGAN.xcm runs Ok on Win7 PC xcskies version
- Use Map Generator to make custom xcm for my "local" Michigan area. Still fails.
- Changed .prf to DrawTerrain?="0" & DrawTopology?="0" (i.e. load xcm file, but dont display anything). Still fails. Also tried combinations DrawTerrain?="0" & DrawTopology?="1" --AND-- DrawTerrain?="1" & DrawTopology?="0"
- Tried changingiPaq memory allocation adn terminating all other running apps.
- Did a COLD reboot of iPaq (unintentional :-( and reinstall of xcsoar. Still fails.
-->> ????
- iPaq HX4700 / Win 2003 Isssue?
- Corrupt data in Open streets near KADG? (Adrian MI US N41-51'10" W084-04'29")
- xcsoar build issue?
-->> xcsoar-startup.log
Free ram 20436 KB
Free storage 38862 KB
Starting XCSoar 6.2-PPC2003
Initialise application instance
Create main window
Initialise graphics
Initialise fonts
Startup dialog
Loading profiles
Loading profile from CF CardXCSoarDataxcsoar-registry.prf
Read registry settings
Units: GetUserDefaultUILanguage() = 0x409
InfoBox? geometry
Create info boxes
Create button labels
Initialise message system
Loading language file
Language: GetUserDefaultUILanguage()=0x409
Loading status file
Loading input events file
Initialise marks
Create map window
OpenTerrain?
Please advise if there is any additional information/test you need me to do.
Attachments
Change History
comment:2 Changed 21 months ago by therzog
Additional testing:
Version: XCSoar-PP2000.cab
Hardware: iPaq 3635
Windows Pocket PC version 3.0.1171 with 31 MB RAM
The US_MICHIGAN.xcm map database WILL load OK. (Same file that fails on the HX4700 device)
comment:3 Changed 21 months ago by max
- Status changed from assigned to closed
- Resolution set to fixed
f40f4b6a26f1c934efee8b46e7be6c83e81e1eeb
comment:4 Changed 21 months ago by max
- Status changed from closed to reopened
- Resolution fixed deleted
Oops, closed the wrong ticket, sorry - I can't reproduce this one.
comment:6 Changed 21 months ago by staylo
#1474 is a duplicate of this issue. Further notes:
This may be linked to a geographic area: The neighbouring pre-generated XCMs US_MICHIGAN, US_ILLINOIS_NO, US_ILLINOIS_SO and US_INDIANA all cause the crash but surrounding XCMs such as US_COLORADO and CAN_SW_ONTARIO do not.
If a cache file generated from 6.1.5 exists, the terrain appears to load correctly. (Problem linked to cache file generation?)
Steps to reproduce:
Clear XCSoarData folder
Add US_ILLINOIS_NO.XCM to XCSoarData folder
Run XCSoar 6.1.5
Configure US_ILLINOIS_NO.xcm as map database
'Loading Terrain' completes successfully, 'Loading Waypoints' appears, crash to desktop (ATTACHMENT: 6.1.5_xcsoar-startup.log)
(ATTACHMENT: 'terrain' from cache/terrain)
Run XCSoar 6.2
XCSoar 6.2 loads normally. (ATTACHMENT: 6.2.1_xcsoar-startup.log)
cache/terrain is unchanged.
comment:8 Changed 19 months ago by Turbo
- Owner changed from max to staylo
please retry with the new uploaded map files from the same url.
comment:9 Changed 19 months ago by staylo
Issue is unchanged, the following maps cause XCSoar to crash as soon as the 'Loading Terrain' message appears at the beginning of startup:
US_ILLINOIS_NO.xcm US_ILLINOIS_SO.xcm US_INDIANA.xcm US_MICHIGAN.xcm
but these maps (geographically close) load correctly:
CAN_SW_ONTARIO.xcm
US_OK_HINTON.xcm
comment:10 Changed 19 months ago by staylo
Problem still occurs if the XCM is extracted and only the terrain.jp2 file is loaded.
comment:11 Changed 17 months ago by therzog
Tried it again on my HX4700/PPC2003 with v6.2.5 and new download of US_MICHIGAN.xcm. Still fails. Will start with a generic default profile, but as soon as I add MI maps, it fails on the restart.
comment:14 Changed 6 months ago by apf
- Status changed from assigned to closed
- Resolution set to fixed
- Description modified (diff)
Probably fixed for #2478. Please reopen if this still occurs after installing 6.4.5 (not yet released).
comment:15 Changed 6 months ago by apf
- Status changed from closed to reopened
- Resolution fixed deleted
- Component changed from Other to Map
Unfortunately does not seem to be caused by the same issue. Reopened.
comment:16 Changed 6 months ago by apf
There are some anomalies during terrain cache creation detected while using the Michigan map (http://download.xcsoar.org/maps/US_MICHIGAN.xcm) on a UNIX build:
==1205== Syscall param write(buf) points to uninitialised byte(s) ==1205== at 0x68F01ED: ??? (in /lib64/libc-2.14.1.so) ==1205== by 0x6894982: _IO_file_write@@GLIBC_2.2.5 (in /lib64/libc-2.14.1.so) ==1205== by 0x6894849: new_do_write (in /lib64/libc-2.14.1.so) ==1205== by 0x6895BD4: _IO_do_write@@GLIBC_2.2.5 (in /lib64/libc-2.14.1.so) ==1205== by 0x6895155: _IO_file_xsputn@@GLIBC_2.2.5 (in /lib64/libc-2.14.1.so) ==1205== by 0x688B01C: fwrite (in /lib64/libc-2.14.1.so) ==1205== by 0x4B7039: RasterTileCache::SaveCache(_IO_FILE*) const (RasterTileCache.cpp:494) ==1205== by 0x4B44E3: RasterMap::RasterMap(char const*, char const*, FileCache*, OperationEnvironment&) (RasterMap.cpp:61) ==1205== by 0x4BA811: RasterTerrain::RasterTerrain(char const*, char const*, FileCache*, OperationEnvironment&) (RasterTerrain.hpp:62) ==1205== by 0x4BA72D: RasterTerrain::OpenTerrain(FileCache*, OperationEnvironment&) (RasterTerrain.cpp:48) ==1205== by 0x4E414F: XCSoarInterface::Startup() (Components.cpp:350) ==1205== by 0x547D82: main (XCSoar.cpp:133) ==1205== Address 0x11192030 is not stack'd, malloc'd or (recently) free'd ==1205== Uninitialised value was created by a stack allocation ==1205== at 0x4B6D7C: RasterTileCache::SaveCache(_IO_FILE*) const (RasterTileCache.cpp:456)
Also some minor rendering glitches are seen at certain zoom levels:
comment:17 Changed 6 months ago by apf
- Owner staylo deleted
- Status changed from reopened to assigned
comment:18 Changed 4 months ago by apf
The problem is probably caused by a bug in the geojasper tool which generates a corrupt jp2 file for this geographic area. The SRTM source tiff height data is correct.
The glitches mentioned in comment 16 are a different issue. Due to the size of the lakes the source data we use splits the lake shape into several segments. The shape simplification xcsoar uses to allow fast rendering of high-resolution shapes at low zoom levels eliminates significant points in the area where the split shapes touch leading to a gap in the displayed lake topography. This is mainly a cosmetic issue.
comment:19 Changed 6 weeks ago by apf
The current version of the pre-generated US_MICHIGAN.xcm is fixed. The online map generator still needs an update however since it still uses the old version of the map generation tools.
comment:20 Changed 6 weeks ago by apf
- Owner set to minad
- Milestone changed from XCSoar 6.4 to # Map Generator
See my osm2shp and mapgen repos on xcsoar.org for updated tools. Note that some external tools (grass / gdal) also need patches.
