Details
-
Bug
-
Resolution: Fixed
-
High
-
7.1.0-OD-05
-
7.01
-
Description
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
This bug is related to JRA-24633,
Problem Description
When customer upload a JPEG which is large (>100MB), it requires a lot of memory to generate the Thumbnail (e.g. in avatar picker) of the image and the instance crashes with OOME.
It would be better if there is an error message or limit handling when it captures the size of the file and drop the thumbnail generation to ensure the instance is still running. Instead of allowing and later the instance crashes everytime the issue is loaded.
In case of avatar picker JIRA should reject request informing user that image is too big and that smaller image should be used.
Steps to replicate
- Get a huge dimension picture file (Eg, 2988 x 5312)
- Upload it as an avatar
- High possibility the instance will run into OOME
Expected Result
To have warning telling that image is too big, or alternatively, drop the thumbnail rendering for the file with error message.
Workaround
To use a smaller size image file for avatar
Attachments
Issue Links
- relates to
-
JRACLOUD-40084 Large Image Files (> 100MB) in avatar picker causing OOME
- Closed
-
JRASERVER-24633 JAC ran out of memory because of a 500MB ImageBuffer which was a thumbnail of an attachment
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- PIR - Priority Action
-
PIR-471 Loading...