Wolfgang Meier

Please note that after removing the trigger – while leaving the rest of the configuration untouched – the restore process went smooth and memory consumption stayed within lower bounds as...

Maybe you get different results because you used `-XX:+HeapDumpOnOutOfMemoryError`, which means that the system was already in a state in which it was fighting for life, thus showing misleading results?...

I managed to track down and fix one indexing issue in #1763, which leads to somewhat similar symptoms. It only applies to elements indexed by and queried through a range...

Ok, would it be possible to provide me a dump of the eXist data dir (just dom.dbx, symbols.dbx, collections.dbx and structure.dbx) of an instance where the issue just became noted?...

If you cannot provide the data (happy to sign a NDA if needed), the only other option would be for us to actually reproduce the issue with a test. Have...

Ok, thanks. This proofs the structural index is indeed the culprit. Now we would just need to find a way to simulate the issue.

I tried to merge this before the last release, but failed. Further investigations are required.

I'm a bit confused because I thought you were going to replace the collection browser in the dashboard? The one in eXide is the one which works fine for me,...

@claudius108 Did you test if your changes work outside the tamboti context, i.e. in an installation with just the wiki, but nothing else?

The workaround is to edit `odd/configuration.xml` (or `resources/odd/configuration.xml` in a generated app) and add the attribute `skip-global="true"` to the modules element: ``.