From: <fli...@go...> - 2014-04-26 06:01:49
|
Status: New Owner: ---- New issue 1456 by wlbr...@cox.net: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 *What steps will reproduce the problem?* 1.try running FG 3.0 or 3.1 after git pull fgdata master 2. 3. *What is the expected output? What do you see instead?* FG to start-up and run. Instead FG launch stuck at "loading nav data". *Any output in the console (black window)?* n/a *What FlightGear version are you using (when using GIT version, please mention date)?* FG 3.0 and FG 3.1 from superbuild/fgdata head *What operating system and graphics card?* Win/64,nVidia GeForce GT640 *Please provide any additional information below or as attachment (Avoid expiring external links, such as to imageshack/pastebin/...).* The C:\Users\user\AppData\Roaming\flightgear.org\navdata_3_0.cache keeps growing and never stops. I killed FG when navdata_3_0.cache reached over 5 gig. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-04-26 15:27:53
|
Comment #1 on issue 1456 by p...@freeflightsim.org: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 From my experience it takes a long time. I wish there was some progress bar and some text eg "Preparing navdata, this can take a long time" or alike -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-04-26 16:18:13
|
Comment #2 on issue 1456 by wlbr...@cox.net: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 This is beyond "a long time". This is indefinite. It appears it will keep growing until hard drive is eaten up. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-04-26 20:05:14
|
Comment #3 on issue 1456 by wlbr...@cox.net: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 After process of elimination I think I narrowed it down to poi.dat.gz. If I replace the original poi.dat.gz file with a copy of same from a working 3.0 fgdata source, it gets past the navcache build. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-04-26 20:53:53
|
Comment #4 on issue 1456 by wlbr...@cox.net: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 After re-downloading the entire Navaids folder, in an attempt to rule out a corrupt file, the infinite cache building is back. However replacing poi.dat.gz with a 3.0 version has no effect this time. But thru process of elimination a second time replacing existing master fgdata navaids gz files with 3.0 files in the following order poi.dat.gz carrier_nav.dat.gz fix.dat.gz when I got to nav.dat.gz it no longer continues to grow navdata_cache. It is just stuck at 60 meg and has stopped there, failing to finish loading FG. That's all I got, I'm done for now. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-04 18:11:15
|
Comment #5 on issue 1456 by ral...@rogers.com: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 I have run into exactly this too. I traced it to an infinite while-loop in which for some reason eof() is never true, even though it looks (to me) like 0 chars remain in the stream when I step throught the code. Within the loop the function readNavFromStream() writes to navdata_cache and since the loop doesn't end that file keeps growing: --------- In navdb.cxx: loadCarrierNav() .. opens file Navaids/carrier_nav.dat.gz .. while ( ! incarrier.eof() ) { // force the type to be MOBILE_TACAN readNavFromStream(incarrier, FGPositioned::MOBILE_TACAN); } ---------- I wonder is there any way this could be related to the new zlib being used... is zlib used to read the .gz files, or is it just some kind of corruption in the .gz file? Works fine if I bypass loading the file. My specs: win8.1 MSVS2010/SP1 CMake superbuild-windows clean May 3, 2014, fgdata pull May 3, 2014 fgmeta: next + Applied fix for BUG 1458 built FlightGear-Meta.sln and then FlightGear.sln debug x64 trace -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-04 22:05:30
|
Comment #6 on issue 1456 by wlbr...@cox.net: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 I'm not sure if I did something weird in downloading the gz's from git or if they are gz inside of gz's. Try opening gz file in compression program and then viewing .dat file. It is binary (another gz, but named .dat). At least mine is. I tried to sort that out but still didn't work. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-04 22:37:40
|
Comment #7 on issue 1456 by ral...@rogers.com: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 **** Found Problem + temporary workaround: The [carrier_nav.dat] file within [carrier_nav.dat.gz] is a plain text file editable using for example windows notepad. **** The code apparently can't handle reading embedded comments or blank lines in the middle of the embedded .dat file. **** Workaround: Extract [carrier_nav.dat] and edit it to remove the comment and blank lines and then re-archive it into [carrier_nav.dat.gz] (ie, replace original carrier_nav.dat inside the archive - I was able to do this using 7-zip on windows). ---- Example My original carrier_nav.dat starting on next line ------------------ 12 999 999 100 10890 0 0.0 FCH FNS Foch TACAN 12 999 999 100 10895 0 0.0 CLM FNS Clemenceau TACAN 12 999 999 100 10900 0 0.0 CDG FNS Charles_de_Gaulle TACAN # Most US carriers use AN/URN-25 TACAN with a nominal range of 300NM 12 999 999 100 10925 300 0.0 NMZ USS Nimitz TACAN 12 999 999 100 10935 300 0.0 ESN USS Eisenhower TACAN 12 999 999 100 10920 300 0.0 VIN USS Vinson TACAN 12 999 999 50 10910 300 0.0 SAN USS San Antonio TACAN 12 999 999 0 11030 200 0.0 ES1 ESSO1 TACAN 12 999 999 0 11040 200 0.0 ES2 ESSO2 TACAN 12 999 999 0 11050 200 0.0 ES3 ESSO3 TACAN 12 999 999 0 11130 200 0.0 TE1 TEXACO1 TACAN 12 999 999 0 11140 200 0.0 TE2 TEXACO2 TACAN 12 999 999 0 11150 200 0.0 TE3 TEXACO3 TACAN 12 999 999 0 102100 200 0.0 MB1 MOBIL1 TACAN 12 999 999 0 102200 200 0.0 MB2 MOBIL2 TACAN 12 999 999 0 102300 200 0.0 MB3 MOBIL3 TACAN ------------------------- ended on empty line above ---------------------------- Replacement data starting on next line --------------------------------------------- 12 999 999 100 10890 0 0.0 FCH FNS Foch TACAN 12 999 999 100 10895 0 0.0 CLM FNS Clemenceau TACAN 12 999 999 100 10900 0 0.0 CDG FNS Charles_de_Gaulle TACAN 12 999 999 100 10925 300 0.0 NMZ USS Nimitz TACAN 12 999 999 100 10935 300 0.0 ESN USS Eisenhower TACAN 12 999 999 100 10920 300 0.0 VIN USS Vinson TACAN 12 999 999 50 10910 300 0.0 SAN USS San Antonio TACAN 12 999 999 0 11030 200 0.0 ES1 ESSO1 TACAN 12 999 999 0 11040 200 0.0 ES2 ESSO2 TACAN 12 999 999 0 11050 200 0.0 ES3 ESSO3 TACAN 12 999 999 0 11130 200 0.0 TE1 TEXACO1 TACAN 12 999 999 0 11140 200 0.0 TE2 TEXACO2 TACAN 12 999 999 0 11150 200 0.0 TE3 TEXACO3 TACAN 12 999 999 0 102100 200 0.0 MB1 MOBIL1 TACAN 12 999 999 0 102200 200 0.0 MB2 MOBIL2 TACAN 12 999 999 0 102300 200 0.0 MB3 MOBIL3 TACAN ------------------------- ended on empty line above ---------------------------- -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-04 23:51:23
|
Comment #8 on issue 1456 by wlbr...@cox.net: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 Wish I could verify this but it didn't work on mine. It still is in an infinite loop. I even tried doing the same with poi.dat.gz and TACAN_freq.dat.gz. The other gz files are formatted differently. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-05 00:34:18
|
Updates: Status: NeedInfo Cc: zak...@ma... Comment #9 on issue 1456 by NasalMusician: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-05 01:34:22
|
Comment #10 on issue 1456 by ral...@rogers.com: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 In my case changing to the clean file (attached) cured it. But readNavFromStream() gets used for other files too so I guess my workaround is rather limited. Tracing: while ( ! incarrier.eof() ) { // force the type to be MOBILE_TACAN readNavFromStream(incarrier, FGPositioned::MOBILE_TACAN); } the error appears to me as follows: a) First three lines of file were read correctly in while loop b) readNavFromStream() now encounters empty line and improperly reads at 144/145 placing nonsense into the variables c) subsequent code processes and adds into cache, which grows that file d) function returns e) calling while loop does not detect eof() e) ... function called again f) 133..137 do NOT result in return at 138 g) 144/145 read in nonsense etc all subsequent iterations read nonsense and fail to detect eof(). 133 NavDataCache* cache = NavDataCache::instance(); 134 135 int rawType; 136 aStream >> rawType; 137 if (aStream.eof() || (rawType == 99)) { 138 return 0; // happens with, eg, carrier_nav.dat 139 } 140 141 double lat, lon, elev_ft, multiuse; 142 int freq, range; 143 std::string name, ident; 144 aStream >> lat >> lon >> elev_ft >> freq >> range >> multiuse >> ident; 145 getline(aStream, name); .. Attachments: carrier_nav.dat.gz 301 bytes -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-05 18:01:20
|
Comment #11 on issue 1456 by wlbr...@cox.net: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 To double check I used your file (in case the line endings were different from mine). Still no luck. A little more info in my case. I thought this started with an update of fgdata (master), but now the FG Meta SuperBuild is doing the same thing with 3.0 fgdata. After doing another pull, it looks like someone cleaned the blank line and comment from carrier_nav.dat.gz. This has not solved my problem. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-05 23:17:40
|
Comment #12 on issue 1456 by ral...@rogers.com: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 Sometime in the next few days I'll scrounge up some time to do (yet another) complete clean clone of fgmeta and fgdata and start-from-scratch build to see if I can still duplicate this issue and to hopefully find out where it's something more than what I've previously found above. Don't forget, this thing is constantly changing and sometimes it's like bobbing for apples... -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-06 17:25:44
|
Comment #13 on issue 1456 by wlbr...@cox.net: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 Really strange, I never did try to just remove carrier_nav.dat.gz from the Navdata folder. So I just did and now both 3.0 FG binary and FG master from git work with 3.1.0 fgdata. So my system won't work with a clean carrier_nav.dat.gz but will if I just remove it. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-09 01:30:41
|
Comment #14 on issue 1456 by ral...@rogers.com: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 I suggest this case be closed unless someone disagrees. May 7, 2014: I can no longer reproduce the issue in a release build when I do everything *completely from scratch*. Followed the Windows CMAKE Superbuild sequence to perform a Windows x64 release build of fgmeta / FlightGear-Meta.sln (FlightGear/next: at commit b80b010), and then run fgrun using fresh clone fgdata. I also first cleaned out the [Users]/.../[Roaming]/[FlighGear.org], FG_ROOT/[Scenery] and FG_ROOT/[TerraSync] folders to remove all earlier downloaded scenery and saved preferences in an effort to duplicate a clean first-time install. The application successfully created and populated navdata_cache and prefs file(s), downloaded scenery etc. and then ran simulation. Several times. On further reflection, the debug data values and trace behaviour (eof or lack therof) I described earlier are now highly suspect as I'm sure the values I obtained/read were affected by running thread timers and probably locks etc. The upshot of all the above is I'm uncertain as to the combination of data or circumstances that will again definitely lead to the behavior I/we actually encountered, other than that it has something to do with a cache rebuild performed using carrier_nav.dat.gz . And we do know of several workarounds to try if it happens again, one of which is to simply remove the carrier_nav.dat.gz file. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-09 08:42:05
|
Updates: Status: WontFix Comment #15 on issue 1456 by clement....@gmail.com: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 I have no problem here with Win7 and last GIT. I'm closing it, feel you free to re-open a new bug report if needed. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-09 17:37:25
|
Comment #16 on issue 1456 by wlbr...@cox.net: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 Agreed, it appears to be gone for now. Looking back in history this appears to be a reoccurring problem. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-25 12:02:07
|
Updates: Status: New Comment #17 on issue 1456 by aeitsch...@yahoo.de: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 Re-opening! Back again- stuck at carrier nav date: Current GIT (05/25/2014), Jenkins #785, win 8.1, Sony VAIO Laptop with Intel Core i5-3230M a 2,6 Ghz, 6GB RAM, Nvidia GeForce 640 M LE Did not yet tried the solution proposed here, but I expect that FGFS runs out of the box without any further editing. Console output: NavCache at:Path "C:/Users/HoerBird/AppData/Roaming/flightgear.org/navdata_3_1.c ache" will create tables Data file version = 1000 apt.dat load took:33315 fix.dat load took:11834 findAirportRunway: unknown airport/runway:EDRZ 3 ILS-cat-I findAirportRunway: unknown airport/runway:EHVK 6L ILS-cat-I findAirportRunway: unknown airport/runway:KBXM 1R ILS-cat-I findAirportRunway: unknown airport/runway:KIAD 1L ILS-cat-I findAirportRunway: unknown airport/runway:EDRZ 3 GS findAirportRunway: unknown airport/runway:EHVK 6L GS findAirportRunway: unknown airport/runway:KBXM 1R GS findAirportRunway: unknown airport/runway:KIAD 1L GS findAirportRunway: unknown airport/runway:32L GS findAirportRunway: unknown airport/runway:03 GS findAirportRunway: unknown airport/runway:EDRZ 3 OM findAirportRunway: unknown airport/runway:EDRZ 3 MM findAirportRunway: unknown airport/runway:KIAD 1L IM nav.dat load took:4749 stage 1 commit took:2943 SKIPPING POI load on Windows opening file: C:/Users/HoerBird/Documents/FlightGear/fgdata/Navaids/carrier_nav. dat.gz -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-25 12:24:39
|
Comment #18 on issue 1456 by aeitsch...@yahoo.de: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 With removing carrier_nav.dat.gz it works like charme. Interesting.... -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
From: <fli...@go...> - 2014-05-25 20:21:31
|
Comment #19 on issue 1456 by wlbr...@cox.net: FG launch stuck at "loading nav data" caused by git pull of fgdata master http://code.google.com/p/flightgear-bugs/issues/detail?id=1456 With certain configurations removing carrier_nav.dat.gz is not an option. I don't know what make it required sometimes and at other times it's not. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |