Body: <p>I have a front-end form to upload image files, which works 100% perfectly most of the time. However, I've noticed with larger sized images, I'll get a PHP error saying:</p>
  
  <pre><code>PHP warning
  include(pathToCraft/craft/app/vendor/lsolesen/pel/src/PelInvalidDataException.php): failed to open stream: No such file or directory 
  </code></pre>
  
  <p>I'm not sure if this is an issue on my end or Craft. Should I be expirementing which file size starts causing this and restricting uploads from surpassing that limit in the plugin before saving entry?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-01T20:37:16.767Z
Comments.Text: Yeah, you may want to do a few tests and try to narrow down the file size threshold. The error message doesn't directly indicate a size issue, but it's certainly possible.
Comments.UserDisplayName: Lindsey D
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-01-01T23:57:41.833Z
Comments.Text: Also probably worth swapping from GD => Imagick (or visa-versa) to see if it's your underlying image processing library that's choking.
Comments.UserDisplayName: Brad Bell
Tags: <assets><error-message><php><upload>
Title: PHP Warning on Asset Upload: PelInvalidDataException
ThreadText: # PHP Warning on Asset Upload: PelInvalidDataException
  
  (Asked by: username_0 on 2016-01-01)
  
  I have a front-end form to upload image files, which works 100% perfectly most of the time. However, I've noticed with larger sized images, I'll get a PHP error saying:
  
  ```
  PHP warning
  include(pathToCraft/craft/app/vendor/lsolesen/pel/src/PelInvalidDataException.php): failed to open stream: No such file or directory 
  
  ```
  
  I'm not sure if this is an issue on my end or Craft. Should I be expirementing which file size starts causing this and restricting uploads from surpassing that limit in the plugin before saving entry?
  
  **Tags:** assets, error-message, php, upload
  
  > **Comments:**
  > **username_1**: Yeah, you may want to do a few tests and try to narrow down the file size threshold. The error message doesn't directly indicate a size issue, but it's certainly possible.  
  > **username_2**: Also probably worth swapping from GD => Imagick (or visa-versa) to see if it's your underlying image processing library that's choking.  
  
  ---
  
  ## 0 answers
  
  