Server: Searching among thousands of files freezes and web browser crashes

Created on 30 Oct 2018  Â·  8Comments  Â·  Source: nextcloud/server

Steps to reproduce

  1. Search in folder with thousands of files

Expected behaviour

Search works and you are able to find what you are looking for

Actual behaviour

Search freezes and the browser crashes

Server configuration

<?php
$CONFIG = array (
  'passwordsalt' => '*',
  'secret' => '*',
  'trusted_domains' => 
  array (
    0 => '*',
  ),
  'datadirectory' => '/var/www/nextcloud-2/data',
  'overwrite.cli.url' => '*',
  'dbtype' => 'mysql',
  'version' => '14.0.0.19',
  'installed' => true,
  'dbname' => 'nxdb2',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'nxdb2',
  'dbpassword' => '*',
  'instanceid' => 'AAAAAAAAAAAAAAAAAAAAAA',
  'objectstore' => 
  array (
    'class' => 'OC\\Files\\ObjectStore\\S3',
    'arguments' => 
    array (
      'bucket' => '*',
      'autocreate' => true,
      'key' => '*',
      'secret' => '*',
      'hostname' => '*',
      'port' => 443,
      'use_ssl' => true,
      'region' => 'optional',
      'use_path_style' => true,
      'forcessl' => true,
      'overwriteprotocol' => 'https',
    ),
  ),
  'updater.release.channel' => 'beta',
  'maintenance' => false,
  'theme' => '',
  'loglevel' => 2,
);

Operating system:
server Debian 9, client win10

Web server:
Apache 2.4.5
NX 14 / 13 (related too)

Database:
mysql

PHP version:
PHP 7.0.27-0+deb9u1 (cli) (built: Jan 5 2018 13:51:52) ( NTS )

Nextcloud version: (see Nextcloud admin page)
14.0.0.19

Updated from an older Nextcloud/ownCloud or fresh install:
Fresh install

Where did you install Nextcloud from:
Github

bug

Most helpful comment

Search freezes and the browser crashes

Do you by any chance know why it freezes? Are there too many elements on the page? Is the response never returning?

IMO we should address the root cause (why it freezes) and not hide it behind yet another config option (as proposed in #12143).

See also my arguments in https://github.com/nextcloud/server/pull/12065#issuecomment-433391261

cc @nextcloud/designers for some input here

@skjnldsv @danxuliu for the performance problems here.

All 8 comments

GitMate.io thinks possibly related issues are https://github.com/nextcloud/server/issues/3271 (inefficient file search), https://github.com/nextcloud/server/pull/9925 (Select only searched files), https://github.com/nextcloud/server/issues/10711 (Upload Problem on Web Browsers), https://github.com/nextcloud/server/pull/12041 (Properly hide files when searching), and https://github.com/nextcloud/server/issues/8200 (some browser can't download files!).

Search freezes and the browser crashes

Do you by any chance know why it freezes? Are there too many elements on the page? Is the response never returning?

IMO we should address the root cause (why it freezes) and not hide it behind yet another config option (as proposed in #12143).

See also my arguments in https://github.com/nextcloud/server/pull/12065#issuecomment-433391261

cc @nextcloud/designers for some input here

@skjnldsv @danxuliu for the performance problems here.

Do you by any chance know why it freezes? Are there too many elements on the page? Is the response never returning?

My guess.
The filtering we use is pretty bad performance wise :(

Do you by any chance know why it freezes? Are there too many elements on the page? Is the response never returning?

Honestly, no idea. The searching just takes too long time or it just freezes and crash.

IMO we should address the root cause (why it freezes) and not hide it behind yet another config option (as proposed in #12143).

Indeed. But this could be temporarily solution until it is properly fixed. IMO this solution is quite simple and you can use it if you want.

Also, in corporate systems it is usual that you can seach by certain number of chars.

Agree with @MorrisJobke – this is a technical issue which needs to be properly fixed. A configuration option makes no sense here since then _everyone_ would have to fix it for themselves. ;)

Indeed. But this could be temporarily solution until it is properly fixed. IMO this solution is quite simple and you can use it if you want.

That's why I said, that you can use it in your system just fine, but we will not merge it into our product because then we need to maintain if for ever. People use it then and complain that we take "features" from them. Just to let you know why we act in that way.

I just found this issue here: #6861

Duplicate of #6861

Was this page helpful?
0 / 5 - 0 ratings