Ticket hangs when loading

[FreeMacs]

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

Version

10.0.11

Bug description

A technician added photos with a description to a ticket. After that, the entire ticket could no longer be loaded. When opening the ticket, only an endless loading screen appeared.

The ticket could only be exited again after a very long wait. Closing the browser did not help either. After we restarted the server, we were then able to access the content of the ticket with a waiting time of 10 minutes. The comment field where the photos and the technician's comments should be was empty and could only be deleted after a very long wait. After deleting it, everything worked normally again.

Relevant log output

No response

Page URL

No response

Steps To reproduce

Unfortunately, I cannot reproduce the problem

Your GLPI setup information

No response

Anything else?

No response

[efriastech]

Hello, this issue might be related to the one I mentioned, so it would be worth following the development of this entry as well: #16444

Thank you.

[FreeMacs]

I can reproduce the problem.

When I drag and drop an image into this field, there are several behaviors in GLPI.

Images up to approx. 500KB are displayed without any problems.

For images between 600KB and 4MB I only get an empty field.

and with images that are over 4-5MB in size, the ticket can no longer be opened and it just loads endlessly.

If I drag files and photos into the drag and drop field, it works without any problems.

The image is always displayed when I drag it in and it also says Upload Succesful, but after saving it, the specified problems occur.

Is this an error in the text field? Is it not even intended for this? And if not, shouldn't this function be disabled immediately and only be possible via the drag and drop field?

[FreeMacs]

I have now found out with an API query that if you load the photos directly into the comment field, they are probably stored base64 encoded directly in the database and this probably leads to the error.

After this follow-up has been deleted via the API, I can open the ticket again.

[github-actions]

There has been no activity on this issue for some time and therefore it is considered stale and will be closed automatically in 10 days.

If this issue is related to a bug, please try to reproduce on latest release. If the problem persist, feel free to add a comment to revive this issue.
If it is related to a new feature, please open a topic to discuss with community about this enhancement on suggestion website.

You may also consider taking a subscription to get professionnal support or contact GLPI editor team directly.