nextcloud / nextcloud/polls

Re-opened: Long Waiting Time when looking for a name/mailadress to share a poll with

Open
#4,614 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

awaiting feedback needs approval
Dominant language
JavaScript
Stars
284
Forks
91
Avg merge
4d 3h
Merged PRs (30d)
50

Description

⚠️ This issue respects the following points: ⚠️
  • This is a bug, not a question or a configuration/webserver/proxy issue.
  • This issue is not already reported on Github (I've searched it).
  • I agree to follow Nextcloud's Code of Conduct.
What went wrong, what did you observe?

Previously reported two years ago in closed Issues 3366 and 3785

When you search for another user under the "share" section of a Poll it takes a lot of time and certain names cannot be found.
In a few cases it showes no user, when there are over 25 users with this name.

I was not able to recreate a specific pattern of names where this issue occours.
Appereantly searching for the first name of a person triggers this issue easily.

What did you expect, how polls should behave instead?

Same search behaviour as in files app, where lookup of the same users works without noticable delay

What steps does it need to replay this bug?
  1. create poll (text or date doesnt matter)
  2. click on "share" under the poll's details
  3. Search for different names (preferrably names with many results and first names)
Affected polls version

8.6.3

Installation method

Installed/updated from the appstore (Apps section of your site)

Installation type

Updated from a minor version within same major version (i.e. 8.0.0 to 8.1.2)

Can you rule out that any extension you use is involved in the issue?
  • I have checked all browser extension
Which browser did you use, when experiencing the bug?
  • Firefox
  • Chrome
  • Chromium/Chromium based (i.e. Edge)
  • Safari
  • Other/Don't know
Other browser

No response

Add your browser log here

Additional client environment information

Has been reproduced on various client configurations

NC version

Nextcloud 32 (Hub 25 Autumn)

Other Nextcloud version

No response

PHP engine version

Other/Don't know

Other PHP version

No response

Database engine

MariaDB

Database Engine version or other Database

No response

Which user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other/Don't know
Add your nextcloud server log here
{
   "reqId": "iCgwGBS2P5jpFiHdO1kU",
   "level": 3,
   "time": "2026-02-25T11:57:09+00:00",
   "remoteAddr": "***REMOVED SENSITIVE VALUE***",
   "user": "***REMOVED SENSITIVE VALUE***",
   "app": "core",
   "method": "GET",
   "url": "/index.php/apps/polls/search/users/m?types=99",
   "scriptName": "/index.php",
   "message": "Request used 1.7 GB of memory. Memory limit: 2048M",
   "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:148.0) Gecko/20100101 Firefox/148.0",
   "version": "32.0.6.1",
   "data": {
       "app": "core"
   }
}
Additional environment informations

OIDC auth provider
5 digit user base

Configuration report

List of activated Apps

Nextcloud Signing status

Additional Information

Other than the requests high consumption Memory, nothing could be found in logs.
Is there any additional relevant information we can provide?

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 by tracing the /index.php/apps/polls/search/users/{query}?types=99 endpoint used by the poll sharing search, especially with LDAP/Active Directory and large user bases. Reproduce searches for common first names and compare the behavior with the Files app; done means matching users are returned promptly without excessive memory use.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, backend, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.