Opened 7 years ago

Closed 7 years ago

#920 closed defect (fixed)

gosmore stuck in a loop with 100% cpu

Reported by: kalxas Owned by: hamish
Priority: normal Milestone: OSGeoLive6.0RC1
Component: OSGeoLive Keywords: 6.0, gosmore
Cc: live-demo@…

Description

gosmore is causing 100% CPU and does not complete startup

Change history (8)

comment:1 Changed 7 years ago by hamish

Owner: changed from live-demo@… to hamish
Status: newassigned

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.

Hamish

comment:2 Changed 7 years ago by kalxas

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 Changed 7 years ago by hamish

disabled from the build until I rebuild the deb without optimization enabled. (r8153)

Hamish

comment:4 Changed 7 years ago by kalxas

Priority: majornormal

Thanks Hamish

comment:5 Changed 7 years ago by hamish

Keywords: gosmore added
Summary: gosmore crashinggosmore stuck in a loop with 100% cpu

Hi,

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/.

Hamish

comment:6 Changed 7 years ago by kalxas

Thanks for the fix Hamish. I confirm it works on rev 8188. Perhaps we should close this one.

comment:7 Changed 7 years ago by kalxas

Milestone: OSGeoLive6.0RC1

comment:8 Changed 7 years ago by hamish

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.