New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Infinite loop in ExceptionSerializer::removeValuesFromArgs() (NC 19) #23429
Comments
As explained in nextcloud/cms_pico#149 I will close this issue. It turned out to be a red herring. Sorry for the noise! |
@sm8ps I'll reopen this, that |
I agree, the faulty behavior is indeed real. When I replace the new and working version of 'appdata_###/cms_pico' with the old one, the error crops up in a reproducible fashion. So the bug does seem in some way related to cms_pico. If anybody wants to try it out then I can provide a copy of the broken 'cms_pico/'. My capabilities in trouble shooting are too limited to produce any further insights. |
Yes, the infinite loop is related to Pico without any doubt, however, the underlying issue with the infinite loop is not Pico, but the fact that the exception serializer isn't capable of handling recursive references in arrays. That is an error in Nextcloud that must be fixed. After the error in Nextcloud has been fixed we should see the actual exception that has been thrown - allowing us to investiage the issue. However, if you want to you can provide a copy of your |
I am perfectly with you on everything. From a trouble shooting point of view it would be good to check reproducibility. |
So is it related to server or cms_pico? |
|
This issue is still existing in NC25 with cms_pico 1.0.21 modified to be used with Pico 3. What is the status of the issue? |
Hi, please update to 24.0.9 or better 25.0.3 and report back if it fixes the issue. Thank you! My goal is to add a label like e.g. 25-feedback to this ticket of an up-to-date major Nextcloud version where the bug could be reproduced. However this is not going to work without your help. So thanks for all your effort! If you don't manage to reproduce the issue in time and the issue gets closed but you can reproduce the issue afterwards, feel free to create a new bug report with up-to-date information by following this link: https://github.com/nextcloud/server/issues/new?assignees=&labels=bug%2C0.+Needs+triage&template=BUG_REPORT.yml&title=%5BBug%5D%3A+ |
Steps to reproduce
occ app:update
Expected behaviour
The site should show its content.
Actual behaviour
After a very long time, a HTTP-500 error (internal server error) is shown. The site data has been indeed created in the files. Checking with
top
, a process php-fpm has started running on one CPU core at 100% whose virtual memory increases continuously even after the request has been canceled from the client side.Comments
This issue was originally reported as nextcloud/cms_pico#145. This issue is not about cms_pico but about the infinite loop caused by ExceptionSerializer::removeValuesFromArgs() (cf. the Nextcloud log) although there might be connections that I am unaware of.
Server configuration detail
Operating system: Linux 4.15.0-118-generic #119~16.04.1-Ubuntu SMP Tue Sep 8 14:54:40 UTC 2020 x86_64
Webserver: nginx/1.19.2 (fpm-fcgi)
Database: mysql 10.3.24
PHP version:
7.2.24-0ubuntu0.18.04.6
Modules loaded: Core, date, libxml, openssl, pcre, zlib, filter, hash, Reflection, SPL, sodium, session, standard, cgi-fcgi, mysqlnd, PDO, xml, apcu, apc, bcmath, bz2, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, gmp, iconv, igbinary, imagick, inotify, intl, json, exif, mysqli, OAuth, pdo_mysql, Phar, posix, readline, redis, shmop, SimpleXML, sockets, sysvmsg, sysvsem, sysvshm, tokenizer, wddx, xmlreader, xmlwriter, xsl, zip, Zend OPcache
Nextcloud version: 19.0.4 - 19.0.4.2
Updated from an older Nextcloud/ownCloud or fresh install: Updated from 19.0.3
Where did you install Nextcloud from: unknown
Signing status
Array
(
)
List of activated apps
Configuration (config/config.php)
Are you using external storage, if yes which one: local
Are you using encryption:
Are you using an external user-backend, if yes which one:
Client configuration
Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0
Operating system: Ubuntu 20.04
Logs
Web server error log
Nextcloud log
Browser log
n.a.
The text was updated successfully, but these errors were encountered: