Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting a out of memory error... #39

Closed
fstltna opened this issue Jun 30, 2019 · 4 comments
Closed

Getting a out of memory error... #39

fstltna opened this issue Jun 30, 2019 · 4 comments
Labels
bug Something isn't working

Comments

@fstltna
Copy link

fstltna commented Jun 30, 2019

I have it set up but when starting it I get this:

INFO[0000] Starting mapserver                            version=3.0.0
INFO[0000] Loading default colors                        filename=/colors.txt prefix=colormapping size=704276 useLocal=false
INFO[0000] Loaded default colors                         count=16109
INFO[0000] Migrating database                            filename=mapserver.sqlite prefix=mapobjectdb.sqlite
INFO[0000] Migration completed                           elapsed=4.229358ms prefix=mapobjectdb.sqlite
INFO[0000] Starting http server                          port=8080 webdev=false
INFO[0000] Starting initial rendering job               
fatal error: runtime: out of memory

Any ideas?

@thomasrudin thomasrudin added the bug Something isn't working label Jun 30, 2019
@thomasrudin
Copy link
Contributor

thomasrudin commented Jun 30, 2019

Strange, it should not consume that much memory...
Can you tell me something about your setup:

  • Map-size
  • Map-type (sqlite/postgres)
  • RAM-Size
  • Operating System

If it is possible could you provide a reproduction-world to test on?

Also: can you try to run in debug mode and post the results here afterwards:

mapserver -debug

@fstltna
Copy link
Author

fstltna commented Jul 1, 2019

Ok, I'm not sure of the map size, but I am using sqlite, RAM is 1GB, OS is Ubuntu 16.04. Attached is the debug output...
mapserver_debug.txt

@thomasrudin
Copy link
Contributor

That may be related to:
https://github.com/thomasrudin-mt/mapserver/blob/master/doc/config.md#mapblockaccessormaxitems

Can you try setting the limits in the config file a bit lower:

mapserver.json

{
	"mapblockaccessor": {
		"expiretime": "5s",
		"purgetime": "10s",
		"maxitems": 100
	}
}

Those essentially control how many mapblocks are cached in-memory.
The default is 5000 mapblocks, a setting of 100 should work but is slower during the initial rendering.

@thomasrudin
Copy link
Contributor

no response, closing, feel free to reopen..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants