It shows the white page when I upload a large image. My PHP allow 40mb but my picture size is 3.6m, it can't upload.
 

here is the error
 

The problem is happen at Front page and back end during upload... most of my pictures that I must to upload starts from 3mb -7mb

K2 v2.10.4 [Dev Build 20210205]
PHP version 7.4.15
Database version 5.7.33
GD image library bundled (2.1.0 compatible)
Multibyte string support Enabled
Upload limit 300M
Memory limit 64M

I am using JCE and it uploads without any problem.

Here is the error

Notice: Trying to access array offset on value of type int in /home/admin/public_html/khmercdp.org/media/k2/assets/vendors/verot/class.upload.php/src/class.upload.php on line 2769

thank for your support

+1 here, I've had the same problem for ages! I usually instruct users to scale images down to 1080p before uploading (they usually don' need larger images for their websites anyway), but some of them forget this from time to time, and that's when this error occurs. It's a really old issue, actually, hopefully it can easily be fixed.

increase memory_limit in php.ini

Here is my information

max_execution_time 30
max_file_uploads 40
max_input_nesting_level 64
max_input_time 60
max_input_vars 1000
memory_limit 64M
post_max_size 30M

@saovry, like I said push the memory_limit higher

I increased my memory_limit 64M to memory_limit 1024M, it really helps me to upload a large image now..
I am really thank you..

I hope K2 can fix it with the next release even though some users small memory_limit.

thank u

@Goble002 thank you for insisting on memory_limit, it needed pushing up to 512M in order to process some large images. It sits at 1024M now, not too happy about it, but this was a much larger problem for me than worrying about exhausting resources (which won't happen anyway). So thanks again, you've helped A LOT!

Fotis, thank you very much for further clarification! Not using PHP-FHM at the moment, but will definitely reconfigure Apache in the nearby future. My most troublesome server (regarding this particular problem) is a 6-core Xeon with 32 GB of physical memory running solely as a dedicated web server, so I think I wouldn't face this problem anyway, but it's good to set limits, just in case.