Databases
StackOverflow2013
Postsdbo
POMemory leak in Ajax implementation of a file uploader (Django on Heroku)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMemory leak in Ajax implementation of a file uploader (Django on Heroku)
    primarykey
    data
    text
    <p>I've created an ajax file uploader for Django, but each file uploaded takes up a <strong>big</strong> piece of memory (30-80 mb), and doesn't seem to let it go. </p> <p>We're on Heroku, which allots 512mb of memory per dyno, so I quickly start getting over-memory errors.</p> <p>Here is the Django view code to handle the request:</p> <pre><code>if request.is_ajax(): # the file is stored raw in the request upload = request is_raw = True try: filename = request.GET[ 'add_image' ] except KeyError: return HttpResponseBadRequest( "AJAX request not valid" ) (fileBaseName, fileExtension)=os.path.splitext(filename) uniquename = biz_id + "__" + get_a_uuid() + fileExtension saved = save_upload(upload, uniquename, biz) </code></pre> <p>And here is the save_upload code:</p> <pre><code>try: #BusinessImage is my Django model. It uses django-imagekit to processs #the raw uploaded image into three sizes (plus the original) bi = BusinessImage(name=uploaded.GET.get("name"), business=biz) if not BusinessImage.objects.filter(business=biz).exists(): bi.primary_image = True bi.original_image.save(filename,ContentFile(uploaded.read())) except IOError: # could not open the file most likely return False finally: uploaded.close() return True </code></pre> <p>This code is adapted from <a href="https://stackoverflow.com/questions/4750168/fileupload-with-django"> this post </a> (thanks to Alex Kuhl and Thunder Rabbit).</p> <p>I'm thinking the memory problem might have something to do with django-imagekit or I may not be closing the files properly, but I'm not sure. I'd really appreciate any help.</p> <p>Thanks!</p> <p>Clay</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USClay Wardell
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMemory leak in Ajax implementation of a file uploader (Django on Heroku)
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMemory leak in Ajax implementation of a file uploader (Django on Heroku)
      1. USChris Dutrow
      1. VTFavorite
    3. VO
      singulars
      1. POMemory leak in Ajax implementation of a file uploader (Django on Heroku)
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't think this is directly related to django-imagekit. The leak also exists in django-ajax-uploader which is based on the same js code. See: https://github.com/GoodCloud/django-ajax-uploader/issues/12.
      singulars
      1. POMemory leak in Ajax implementation of a file uploader (Django on Heroku)
      1. USDirk Eschler
    2. CO@DirkEschler -- really appreciate that link, Dirk. django-imagekit does have documented memory problems (see: https://github.com/jdriscoll/django-imagekit/issues/63), but even after migrating away from it I noticed I was still having issues, albeit less severe ones, and your link explains them. Thanks again.
      singulars
      1. POMemory leak in Ajax implementation of a file uploader (Django on Heroku)
      1. USClay Wardell
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload