Opened 11 years ago
Closed 11 years ago
#920 closed defect (fixed)
gosmore stuck in a loop with 100% cpu
|Reported by:||kalxas||Owned by:||hamish|
gosmore is causing 100% CPU and does not complete startup
Change history (8)
comment:1 by , 11 years ago
|Status:||new → assigned|
comment:2 by , 11 years ago
I propose to wait until RC and drop it if not ready until then. This ticket should then be moved to 6.5 version.
comment:3 by , 11 years ago
disabled from the build until I rebuild the deb without optimization enabled. (r8153)
comment:4 by , 11 years ago
|Priority:||major → normal|
comment:5 by , 11 years ago
|Summary:||gosmore crashing → gosmore stuck in a loop with 100% cpu|
I rebuilt the .deb with
apt-get build-dep gosmore mkdir gosmore-build && cd gosmore-build apt-get source gosmore cd gosmore... # edit Makefile, etc to remove -O2 # edit debian/changelog to change version number on top line debuild -i -uc -us -b
and put it up on download.o.o. Now gosmore runs. Maybe I'm using it wrong, but after search for Nottingham I got a distance of 0m but didn't jump to it. had to navigate to 53N 1.5W by hand from 0,0 before I could see the road data. The last position is saved to ~/.gosmore.opt (binary) so as an ugly workaround we could just pre-seed that file from app-conf/osm/.
comment:6 by , 11 years ago
Thanks for the fix Hamish. I confirm it works on rev 8188. Perhaps we should close this one.
comment:7 by , 11 years ago
comment:8 by , 11 years ago
|Status:||assigned → closed|
known problem in the package, see http://bugs.debian.org/652084
If we want to keep it in the release I'll probably have to rebuild it locally with the optimization flags turned off.