"Loading database ..." stuck.

Found a bug in "Everything"? report it here
Debugger
Posts: 78
Joined: Thu Jan 26, 2017 11:56 am

"Loading database ..." stuck.

Postby Debugger » Fri Feb 17, 2017 11:15 am

"Loading database ..." stuck.
Annoying and recurring problem.
Sometimes it works, sometimes not, and so from time immemorial to this are the problems.
I do not want every time "Force rebuild the base" is each time consuming for large disks and very many files.
If something uses a large database from the disk will never be fast.
I wants to use only the physical RAM (fastest)
For comparison, the other tool (no name) uses only physical memory.
Reading for 40+ m files, it needs about 3 minutes.
Do not update any database, it works only on the basis of physical memory (Cashing), so speed is of prime importance.

void
Site Admin
Posts: 3523
Joined: Fri Oct 16, 2009 11:31 pm

Re: "Loading database ..." stuck.

Postby void » Fri Feb 17, 2017 11:25 am

Could you please send some debug information.

Could you please give some more information?
Is Everything unresponsive? is Everything using any CPU or disk?

Please make sure compress database is disabled from Tools -> Options -> Indexes.

To disable the Everything database use the -nodb command line option:
Everything.exe -nodb

This will force Everything to reindex everytime you start it. However, this would be slower than loading the database.

Debugger
Posts: 78
Joined: Thu Jan 26, 2017 11:56 am

Re: "Loading database ..." stuck.

Postby Debugger » Fri Feb 17, 2017 1:02 pm

The application freezes my system. High CPU usage.
Indexing - slow,
Sorting - slow,
Updating the database very slow / stuck
Closing applications slow (100% CPU + high use RAM). High system load.
Everything works extremely slowly.
Latest beta version.
Database disbaled compress.
Performance issue.


This will force Everything to reindex everytime you start it. However, this would be slower than loading the database.

the application will always be too slow, if not only uses physical RAM.
Scanning drive takes too long.



Code: Select all

2017-02-17 13:59:19.750: ntfs volume create list 0.003204 seconds
2017-02-17 13:59:19.752: copy config
2017-02-17 13:59:19.752: fire create events
2017-02-17 13:59:19.752: start rebuild thread
2017-02-17 13:59:19.752: create thread
2017-02-17 13:59:19.752: EVENT: 0000000140050870 00000000002d9940
2017-02-17 13:59:19.752: rebuild thread started
2017-02-17 13:59:19.752: build fs list
2017-02-17 13:59:19.752: EVENT: 0000000140050820 00000000002d9940
2017-02-17 13:59:19.752: new results
2017-02-17 13:59:19.752: build indexes
2017-02-17 13:59:19.752: Indexing \\?\Volume{16da0aaf-7a0d-11e5-9377-806e6f6e6963}, C:,
2017-02-17 13:59:19.752: open volume \\?\Volume{16da0aaf-7a0d-11e5-9377-806e6f6e6963}
2017-02-17 13:59:19.752: EVENT: 00000001400597d0 00000000002d9940
2017-02-17 13:59:19.752: CreateFileW(): GetLastError(): 5: Failed to open volume \\?\Volume{16da0aaf-7a0d-11e5-9377-806e6f6e6963}
2017-02-17 13:59:19.752: opened -1 0.000028
2017-02-17 13:59:19.752: create thread
2017-02-17 13:59:19.752: new thread (1)
2017-02-17 13:59:19.752: _service_client_ioctrl 0, s 0 r 4
2017-02-17 13:59:19.752: EVENT: 0000000140050820 00000000002d9940
2017-02-17 13:59:19.752: new results
2017-02-17 13:59:19.752: _service_client_ioctrl reply 0
2017-02-17 13:59:19.752: open service volume \\?\Volume{16da0aaf-7a0d-11e5-9377-806e6f6e6963}
2017-02-17 13:59:19.752: _service_client_ioctrl 1, s 49 r 0
2017-02-17 13:59:19.752: MSG: 0000000000241214 0402 0000000000000000 0000000000000000
2017-02-17 13:59:19.752: _service_client_ioctrl reply 0
2017-02-17 13:59:19.753: _service_client_ioctrl 19, s 0 r 32
2017-02-17 13:59:19.753: MSG: 0000000000241214 c0ef 0000000000000000 0000000000000000
2017-02-17 13:59:19.753: MSG: 0000000000000000 c03e 0000000000000012 0000000000000000
2017-02-17 13:59:19.753: MSG: 0000000000000000 c03e 0000000000000012 0000000000000000
2017-02-17 13:59:19.753: MSG: 0000000000000000 c03e 0000000000000012 0000000000000000
2017-02-17 13:59:19.753: MSG: 0000000000000000 c03e 0000000000000012 0000000000000000
2017-02-17 13:59:19.753: MSG: 00000000000a1016 1401 0000000000000000 0000000000000000
2017-02-17 13:59:19.753: MSG: 00000000000a1016 1401 0000000000000000 0000000000000000
2017-02-17 13:59:19.753: MSG: 000000000010101a 000f 0000000000000000 0000000000000000
2017-02-17 13:59:19.788: _service_client_ioctrl reply 0
2017-02-17 13:59:19.788: MSG: 00000000000a1016 1401 0000000000000000 0000000000000000
2017-02-17 13:59:19.788: EVENT: 0000000140050870 00000000002d9940
2017-02-17 13:59:19.788: _service_client_ioctrl 17, s 0 r 56
2017-02-17 13:59:19.788: MSG: 0000000000241214 0402 0000000000000000 0000000000000000
2017-02-17 13:59:19.788: _service_client_ioctrl reply 0
2017-02-17 13:59:19.788: _service_client_ioctrl 20, s 4 r 0
2017-02-17 13:59:19.788: MSG: 00000000000a1016 1401 0000000000000000 0000000000000000
2017-02-17 13:59:19.788: EVENT: 0000000140050870 00000000002d9940
2017-02-17 13:59:19.788: MSG: 0000000000241214 0402 0000000000000000 0000000000000000
2017-02-17 13:59:19.854: MSG: 0000000000100b32 0113 0000000000000005 0000000000000000
2017-02-17 13:59:19.882: MSG: 0000000000100b32 c042 0000000000000000 0000000000000000
2017-02-17 13:59:19.883: MSG: 0000000000100b32 c042 0000000000000000 0000000000000000
2017-02-17 13:59:19.884: MSG: 0000000000100b32 c043 0000000000000002 000000000119b80d
2017-02-17 13:59:19.884: MSG: 0000000000100b32 c043 0000000000000003 000000000119b80d
2017-02-17 13:59:19.884: MSG: 0000000000100b32 c043 0000000000000004 000000000119b80d
2017-02-17 13:59:19.884: MSG: 0000000000100b32 c043 0000000000000005 000000000119b80d
2017-02-17 13:59:19.884: MSG: 0000000000100b32 c042 0000000000000000 0000000000000000
2017-02-17 13:59:19.944: MSG: 0000000000100b32 c042 0000000000000000 0000000000000000
2017-02-17 13:59:20.054: MSG: 0000000000280794 0113 0000000000000001 0000000000000000
2017-02-17 13:59:20.131: MSG: 000000000010101a 0200 0000000000000000 0000000000bc000c
2017-02-17 13:59:20.141: MSG: 000000000010101a 0200 0000000000000000 0000000000e20056
2017-02-17 13:59:20.152: MSG: 000000000010101a 0200 0000000000000000 0000000000fd0092
2017-02-17 13:59:20.163: MSG: 000000000010101a 0200 0000000000000000 00000000010600ad
2017-02-17 13:59:20.174: MSG: 000000000010101a 0200 0000000000000000 00000000010d00c1
2017-02-17 13:59:20.185: MSG: 000000000010101a 0200 0000000000000000 00000000011400cf
2017-02-17 13:59:20.195: MSG: 000000000010101a 0200 0000000000000000 00000000011400d1
2017-02-17 13:59:20.206: MSG: 000000000010101a 0200 0000000000000000 00000000011400d3
2017-02-17 13:59:20.210: MSG: 000000000010101a 0113 000000000000002d 0000000000000000
2017-02-17 13:59:20.225: MSG: 000000000010101a 0200 0000000000000000 00000000011400d4
2017-02-17 13:59:20.272: MSG: 00000000002c0d8a 0118 000000000000ffff fffff9600013e5f0
2017-02-17 13:59:20.698: MSG: 000000000010101a 0113 000000000000002d 0000000000000000
2017-02-17 13:59:20.724: MSG: 000000000010101a 0200 0000000000000000 00000000011400d4
2017-02-17 13:59:20.726: MSG: 000000000010101a 0200 0000000000000000 00000000011400d4
2017-02-17 13:59:20.802: MSG: 00000000002c0d8a 0118 000000000000ffff fffff9600013e5f0
2017-02-17 13:59:21.109: MSG: 000000000010101a 0200 0000000000000000 00000000011500d4
2017-02-17 13:59:21.121: MSG: 000000000010101a 0200 0000000000000000 00000000011600d4
2017-02-17 13:59:21.132: MSG: 000000000010101a 0200 0000000000000000 00000000011d00d4
2017-02-17 13:59:21.143: MSG: 000000000010101a 0200 0000000000000000 00000000012a00d4
2017-02-17 13:59:21.154: MSG: 000000000010101a 0200 0000000000000000 00000000013c00d4
2017-02-17 13:59:21.165: MSG: 000000000010101a 0200 0000000000000000 00000000015100d4
2017-02-17 13:59:21.175: MSG: 000000000010101a 0200 0000000000000000 00000000016700d4
2017-02-17 13:59:21.176: MSG: 000000000010101a 0113 000000000000002d 0000000000000000
2017-02-17 13:59:21.186: MSG: 000000000010101a 0200 0000000000000000 00000000018900d8
2017-02-17 13:59:21.197: MSG: 000000000010101a 0200 0000000000000000 00000000019f00d8
2017-02-17 13:59:21.208: MSG: 000000000010101a 0200 0000000000000000 0000000001b700d8
2017-02-17 13:59:21.219: MSG: 000000000010101a 0200 0000000000000000 0000000001d400d8
2017-02-17 13:59:21.229: MSG: 000000000010101a 0200 0000000000000000 0000000001ec00d8
2017-02-17 13:59:21.240: MSG: 000000000010101a 0200 0000000000000000 00000000020200d8
2017-02-17 13:59:21.251: MSG: 000000000010101a 0200 0000000000000000 00000000020f00d8
2017-02-17 13:59:21.262: MSG: 000000000010101a 0200 0000000000000000 00000000021d00d6
2017-02-17 13:59:21.273: MSG: 000000000010101a 0200 0000000000000000 00000000022400d4
2017-02-17 13:59:21.283: MSG: 000000000010101a 0200 0000000000000000 00000000022700d3
2017-02-17 13:59:21.298: MSG: 000000000010101a 0200 0000000000000000 00000000022900d2
2017-02-17 13:59:21.309: MSG: 0000000000080b66 0200 0000000000000000 00000000000200d1
2017-02-17 13:59:21.309: MSG: 0000000000080b66 0200 0000000000000000 00000000000200d1
2017-02-17 13:59:21.332: MSG: 00000000002c0d8a 0118 000000000000ffff fffff9600013e5f0
2017-02-17 13:59:21.336: MSG: 0000000000080b66 0200 0000000000000000 00000000000400d0
2017-02-17 13:59:21.347: MSG: 0000000000080b66 0200 0000000000000000 00000000000700cf
2017-02-17 13:59:21.369: MSG: 0000000000080b66 0200 0000000000000000 00000000000a00ce
2017-02-17 13:59:21.379: MSG: 0000000000080b66 0200 0000000000000000 00000000000d00cd
2017-02-17 13:59:21.392: MSG: 0000000000080b66 0200 0000000000000000 00000000000f00cb
2017-02-17 13:59:21.402: MSG: 0000000000080b66 0200 0000000000000000 00000000001000cb
2017-02-17 13:59:21.413: MSG: 0000000000080b66 0200 0000000000000000 00000000001200cb
2017-02-17 13:59:21.424: MSG: 0000000000080b66 0200 0000000000000000 00000000001400cb
2017-02-17 13:59:21.435: MSG: 0000000000080b66 0200 0000000000000000 00000000001500cb
2017-02-17 13:59:21.446: MSG: 0000000000241214 00a0 000000000000000f 00000000035703e7
2017-02-17 13:59:21.456: MSG: 0000000000241214 00a0 000000000000000f 00000000035b03e7
2017-02-17 13:59:21.467: MSG: 0000000000241214 00a0 000000000000000f 00000000035e03e7
2017-02-17 13:59:21.478: MSG: 0000000000241214 02a2 0000000000000000 0000000000000000
2017-02-17 13:59:21.660: MSG: 000000000010101a 0113 000000000000002d 0000000000000000
2017-02-17 13:59:21.866: MSG: 00000000002c0d8a 0118 000000000000ffff fffff9600013e5f0
2017-02-17 13:59:22.145: MSG: 000000000010101a 0113 000000000000002d 0000000000000000
2017-02-17 13:59:22.394: MSG: 00000000002c0d8a 0118 000000000000ffff fffff9600013e5f0
2017-02-17 13:59:22.482: _service_client_ioctrl reply 0
2017-02-17 13:59:22.482: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.482: _service_client_ioctrl reply 0
2017-02-17 13:59:22.482: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.482: _service_client_ioctrl reply 0
2017-02-17 13:59:22.482: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.482: _service_client_ioctrl reply 0
2017-02-17 13:59:22.483: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.483: _service_client_ioctrl reply 0
2017-02-17 13:59:22.483: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.483: _service_client_ioctrl reply 0
2017-02-17 13:59:22.483: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.483: _service_client_ioctrl reply 0
2017-02-17 13:59:22.483: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.483: _service_client_ioctrl reply 0
2017-02-17 13:59:22.483: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.483: _service_client_ioctrl reply 0
2017-02-17 13:59:22.483: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.483: _service_client_ioctrl reply 0
2017-02-17 13:59:22.483: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.483: _service_client_ioctrl reply 0
2017-02-17 13:59:22.483: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.484: _service_client_ioctrl reply 0
2017-02-17 13:59:22.484: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.484: _service_client_ioctrl reply 0
2017-02-17 13:59:22.484: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.484: _service_client_ioctrl reply 0
2017-02-17 13:59:22.484: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.484: _service_client_ioctrl reply 0
2017-02-17 13:59:22.484: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.484: _service_client_ioctrl reply 0
2017-02-17 13:59:22.484: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.484: _service_client_ioctrl reply 0
2017-02-17 13:59:22.484: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.484: _service_client_ioctrl reply 0
2017-02-17 13:59:22.485: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.485: _service_client_ioctrl reply 0
2017-02-17 13:59:22.485: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.485: _service_client_ioctrl reply 0
2017-02-17 13:59:22.485: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.485: _service_client_ioctrl reply 0
2017-02-17 13:59:22.485: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.485: _service_client_ioctrl reply 0
2017-02-17 13:59:22.485: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.485: _service_client_ioctrl reply 0
2017-02-17 13:59:22.485: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.485: _service_client_ioctrl reply 0
2017-02-17 13:59:22.485: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.485: _service_client_ioctrl reply 0
2017-02-17 13:59:22.486: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.486: _service_client_ioctrl reply 0
2017-02-17 13:59:22.486: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.486: _service_client_ioctrl reply 0
2017-02-17 13:59:22.486: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.486: _service_client_ioctrl reply 0
2017-02-17 13:59:22.486: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.486: _service_client_ioctrl reply 0
2017-02-17 13:59:22.486: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.486: _service_client_ioctrl reply 0
2017-02-17 13:59:22.486: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.486: _service_client_ioctrl reply 0
2017-02-17 13:59:22.486: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.487: _service_client_ioctrl reply 0
2017-02-17 13:59:22.487: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.487: _service_client_ioctrl reply 0
2017-02-17 13:59:22.487: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.487: _service_client_ioctrl reply 0
2017-02-17 13:59:22.487: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.487: _service_client_ioctrl reply 0
2017-02-17 13:59:22.487: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.487: _service_client_ioctrl reply 0
2017-02-17 13:59:22.487: _service_client_ioctrl 21, s 0 r 65536
2017-02-17 13:59:22.487: _service_client_ioctrl reply 0

void
Site Admin
Posts: 3523
Joined: Fri Oct 16, 2009 11:31 pm

Re: "Loading database ..." stuck.

Postby void » Fri Feb 17, 2017 3:35 pm

Thanks for the debug log.

Please try running Everything as administrator:
  • In Everything, from the Tools menu, click Options.
  • Click the General tab.
  • Check Run as administrator.
  • Click OK.

There is a small overhead when communicating with the Everything service, when indexing 40million+ files, this would become a rather large overhead.
The Everything service is not required if you run Everything as an administrator and can be disabled from Tools -> Options -> General -> Everything service.

Debugger
Posts: 78
Joined: Thu Jan 26, 2017 11:56 am

Re: "Loading database ..." stuck.

Postby Debugger » Fri Feb 17, 2017 4:02 pm

void wrote:The Everything service is not required if you run Everything as an administrator and can be disabled from Tools -> Options -> General -> Everything service.


I can not change options[Disable Service and Enable Administrator] during the scan (100% overload), so there is no such possibility.
Application not responding. 100% CPU.
100% CPU usage when I choose "Apply".
Can not restore the application on the Top.
My system and the the mouse pointer stops working.

Image

void
Site Admin
Posts: 3523
Joined: Fri Oct 16, 2009 11:31 pm

Re: "Loading database ..." stuck.

Postby void » Fri Feb 17, 2017 4:14 pm

Thanks for the info.

Please try the following:
  • End the Everything.exe processes:
    • Open task manager (Ctrl + Shift + ESC).
    • Click the Processes tab (or Details tab on Windows 8+)
    • Select Everything.exe and click End task.
      Don't worry if you can't end the Everything.exe service process.
  • From a command prompt (Start -> Run -> cmd)
  • Navigate to your Everything.exe folder (cd c:\program files\Everything)
  • Run Everything with the -uninstall-service and -enable-run-as-admin command line options:
    Everything.exe -uninstall-service -enable-run-as-admin
  • Restart Everything.

Debugger
Posts: 78
Joined: Thu Jan 26, 2017 11:56 am

Re: "Loading database ..." stuck.

Postby Debugger » Fri Feb 17, 2017 4:39 pm

Well, now it's okay.

However:
1. Very slow process Everything.exe to end after exiting Everything.
One or more hard drives am very intensive work (can hear heads much I / O read or write)

2. The application does not work too fast with large data
a)Slow Scanning
b)Slow Sorting


suggests:
Support for scanning multiple physical disk drives in parallel.
uses 1 thread per disk on scanning,
and all threads for searching and sorting.

More segust:
3. Viewing the results in real time

salazor
Posts: 255
Joined: Tue Jun 17, 2014 10:52 am

Re: "Loading database ..." stuck.

Postby salazor » Fri Feb 17, 2017 5:16 pm

Debugger wrote:More segust:
3. Viewing the results in real time

You have checked "search as you type" in Options - UI tab?

void
Site Admin
Posts: 3523
Joined: Fri Oct 16, 2009 11:31 pm

Re: "Loading database ..." stuck.

Postby void » Fri Feb 17, 2017 11:12 pm

1. Very slow process Everything.exe to end after exiting Everything.
One or more hard drives am very intensive work (can hear heads much I / O read or write)


This is to be expected for very large indexes.
Everything completely rewrites the Everything.db to disk on exit.
The size of the Everything.db file written to disk will be about the same as the memory usage of Everything.

2. The application does not work too fast with large data
a)Slow Scanning


Like you said, using multiple threads to index would help.
Indexing should only be done once.

b)Slow Sorting


Enable fast sorting at the cost of more RAM from Tools -> Options -> Indexes.

suggests:
Support for scanning multiple physical disk drives in parallel.
uses 1 thread per disk on scanning,


Thanks for the suggestion, It is on my TODO list.

and all threads for searching and sorting.


Everything already uses all CPUs for searching and sorting.

More segust:
3. Viewing the results in real time


Viewing results in realtime with Everything will depend on your hardware and how many files you index.
For optimal searching with Everything, sort by Name ascending.

Debugger
Posts: 78
Joined: Thu Jan 26, 2017 11:56 am

Re: "Loading database ..." stuck.

Postby Debugger » Sat Feb 18, 2017 12:45 pm

I would like tool where you can quickly find files.
Scanning... C, D, E ... Z + Sorting => It takes a lot of time.
It uses more RAM (6,4GB 100% CPU) than other tools (4,8GB RAM 25%CPU)
The computer does not respond to commands.
Other tool works more stable, faster, and does not freeze the computer (lower consumption of CPU) and uses a few GB Ram less.

void
Site Admin
Posts: 3523
Joined: Fri Oct 16, 2009 11:31 pm

Re: "Loading database ..." stuck.

Postby void » Sun Feb 19, 2017 8:29 am

Scanning... C, D, E ... Z + Sorting => It takes a lot of time.


This should happen only once.

It uses more RAM (6,4GB 100% CPU) than other tools (4,8GB RAM 25%CPU)


Disable extended indexing information:
  • In Everything, from the Tools menu, click Options.
  • Click the Indexes tab.
  • Uncheck Index recent changes.
  • Uncheck Index file size.
  • Uncheck index folder size.
  • Uncheck Index date created
  • Uncheck Index date modified
  • Uncheck Index date accessed.
  • Uncheck Index attributes
  • Uncheck Fast path sort
  • Uncheck Fast extension sort.
  • Click OK.

Debugger
Posts: 78
Joined: Thu Jan 26, 2017 11:56 am

Re: "Loading database ..." stuck.

Postby Debugger » Sun Feb 19, 2017 8:59 am

Now it is showing faster after scanning drives, but still have to wait about ~15 minutes to scan all drives.
This can speed up only a parallel scan.


Return to “Bug report”