nextcloud / nextcloud/maps

[Bug]: Pictures not being processed after 10k

Open
#1,380 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug feature: 🖼 photos performance
Dominant language
JavaScript
Stars
598
Forks
113
PR merge metrics
No merged PRs in 30d

Description

⚠️ This issue respects the following points: ⚠️
Bug description

Hi everyone! 👋
I have a lot of photos in my nextcloud and i want to see them all on the map (the ones with gps data ofc).
I placed the .index.maps in every folder and run the command (occ maps:scan-photos) multiple times now.
Still only 10k of my pictures are loaded. (The popup "… remaining" is gone too)
And I know that i have thousands more with gps data from various trips.

Steps to reproduce
  1. have multiple folders (and folder in folders)
  2. have .index.maps in every (sub)folder
  3. have >>10k photos
  4. run maps:scan-photos
  5. wait
Expected behavior

I would expect them all to be loaded in the map after a reasonable amount of time with a user feedback, like a toast or
best would be a progressbar somewhere.

I expect it to use a fixed and reasonable amount of RAM while processing.

Installation method

Official Docker image

Operating system

Debian/Ubuntu

PHP engine version

None

Web server

None

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install of the server?

None

Is this bug present after an update or on a fresh install of the app?

Fresh Nextcloud Maps install (never installed before)

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report
nothing special.
enabled preview gen.
enabled redis cache.
List of activated Apps
Enabled:
  - activity: 3.0.0
  - app_api: 4.0.5
  - bruteforcesettings: 3.0.0
  - camerarawpreviews: 0.8.6
  - circles: 30.0.0
  - cloud_federation_api: 1.13.0
  - comments: 1.20.1
  - contactsinteraction: 1.11.0
  - dashboard: 7.10.0
  - dav: 1.31.1
  - federatedfilesharing: 1.20.0
  - federation: 1.20.0
  - files: 2.2.0
  - files_3dmodelviewer: 0.0.15
  - files_downloadactivity: 1.17.0
  - files_downloadlimit: 3.0.0
  - files_external: 1.22.0
  - files_pdfviewer: 3.0.0
  - files_reminders: 1.3.0
  - files_sharing: 1.22.0
  - files_trashbin: 1.20.1
  - files_versions: 1.23.0
  - firstrunwizard: 3.0.0
  - integration_excalidraw: 2.4.0
  - integration_paperless: 1.0.5
  - logreader: 3.0.0
  - lookup_server_connector: 1.18.0
  - maps: 1.5.0
  - nextcloud_announcements: 2.0.0
  - notifications: 3.0.0
  - oauth2: 1.18.1
  - password_policy: 2.0.0
  - photos: 3.0.2
  - previewgenerator: 5.7.0
  - privacy: 2.0.0
  - provisioning_api: 1.20.0
  - recommendations: 3.0.0
  - related_resources: 1.5.0
  - serverinfo: 2.0.0
  - settings: 1.13.0
  - sharebymail: 1.20.0
  - support: 2.0.0
  - survey_client: 2.0.0
  - systemtags: 1.20.0
  - text: 4.1.0
  - theming: 2.5.0
  - twofactor_backupcodes: 1.19.0
  - updatenotification: 1.20.0
  - user_status: 1.10.0
  - viewer: 3.0.0
  - weather_status: 1.10.0
  - webhook_listeners: 1.1.0-dev
  - workflowengine: 2.12.0
Nextcloud Signing status

Nextcloud Logs
This is the key:

Fehler	PHP	
Allowed memory size of 1610612736 bytes exhausted (tried to allocate 12934200 bytes) at /var/www/html/custom_apps/maps/lib/Helper/ExifGeoData.php#114
Browser Console

Additional info

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the maps:scan-photos command and inspect custom_apps/maps/lib/Helper/ExifGeoData.php at line 114, where the reported memory exhaustion occurs. Reproduce with nested folders and more than 10k geotagged photos, then verify that scanning completes without exhausting memory and processes all eligible photos.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.