Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Merkaartor 0.13.1 unusable: High cpu, whole operating system becomes unresponsive #1691

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments

Comments

@openstreetmap-trac
Copy link

Reporter: soc
[Submitted to the original trac issue database at 2.15pm, Sunday, 5th April 2009]

I went to the merkaartor homepage and built me a package from the current version (0.13.1).

But this version uses an insane amount of cpu. While merkaartor works (e.g. downloading one or two tiles which takes approx. 20(!) seconds each), my whole display is completely frozen and doesn't respond anymore.

I went back to merkaartor 0.12, which is the last version which works for me. (I downloaded the merkaartor package 0.13 from Debian, but that version gave me a SegFault right after starting the app.)

OS: Ubuntu 8.10 (amd64)
CPU: Intel Core 2 Duo E4400
GPU: Nvidia Geforce 8500 GT

@openstreetmap-trac
Copy link
Author

Author: bielawski1[at]gmail.com
[Added to the original trac issue at 10.12pm, Sunday, 5th April 2009]

I do see a major slowdown with 0.13, but it is still usable for me. With 0.12, I could get render times of 5 to 10 ms; now they are closer to 60 ms. I'm on Debian unstable, Intel Core Duo T2050, Intel 945GM.

@openstreetmap-trac
Copy link
Author

Author: koying
[Added to the original trac issue at 11.28pm, Sunday, 5th April 2009]

It looks like there are problems with nvidia cards on linux.

Please add "NVIDIA_HACK=1" to you "qmake" command.

@openstreetmap-trac
Copy link
Author

Author: soc
[Added to the original trac issue at 5.59pm, Wednesday, 8th April 2009]

I switched from nvidia-glx-177 to nouveau and the problem was gone. I can now confirm that this is a nvidia driver bug. It might be interesting if the bug is fixed in nvidia-glx-180...

@openstreetmap-trac
Copy link
Author

Author: koying
[Added to the original trac issue at 7.04pm, Wednesday, 8th April 2009]

Replying to [comment:3 soc]:

I switched from nvidia-glx-177 to nouveau and the problem was gone. I can now confirm that this is a nvidia driver bug. It might be interesting if the bug is fixed in nvidia-glx-180...

Forwarding to the list as it might interest others...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant