i noticed that mac and the flash-plugin gets in conflict when doing multiple uploads.
There's no problem when it's only 3 or 5 files, but when the amount of files is higher then uploadify just stops uploading. The plugin kinda crashes.
Strangely on windows there is no single problem with multiple uploading.
I upgraded Flash, both on mac and windows. I checked the sessions-id's, i checked this forum, the forum at uploadify.
But can't find where to search for...
Can somebody give me some clues about what to do.
Thanks,
Dave
I am also using uploadify v3.2.1. I came here looking into why it isn't working for some mac users, but stumbled upon your question and seeing it has no feedback on it, I will try to point you onto something that could be a solution....
Are you using PHP? If yes; Did you verify that the total post size is not going above what is allowed for php?
The php.ini file has the setting for post size limit, if the amount of images in one request goes beyond that which is set in the php.ini, it may be causing this, as you only get it when uploading more than 3-5 files (which can amount to a size over that limit) and not when uploading less than that... try raising the post size limit and then retrying the upload file-set that fails right now...
Related
I have been using my antique pc with a bit of stress at times and full of gratefulness at other times, but starting from yesterday, my old pc began stressing me out, and, most importantly, I couldn't fix it just by following a few tutorials on the internet.
Yesterday, when I wanted to draft some emails on Gmail from MS Edge, which I have been using since it is considered the most RAM-friendly, it crashed, and the crash continued no matter how many times I refreshed the page or restarted the pc. It says the error code: Out of memory
Sure enough, opening the task manager tab, I saw that MS Edge was using about 3000000k or 300 Mb, and it also displayed roughly 90% of memory was being used when the Gmail tab is only open and no other activity was going on. For a different person, the result may seem obvious, but my pc has been working somewhat ok, at least it wouldn't crash for just opening a Gmail tab and drafting an email. Therefore, it is not a normal occurrence from my perspective.
Do you know what is the strangest thing? My PC's performance has gotten better; for example, while asking this question, nothing happened, and it is responding extremely quickly as if I am working on the latest laptop haha. Then, what happens when entering Gmail?
Ok, here are a few pictures that may be useful.
When I try to get an ajax response around 100 mb I get this error:
Error: Could not complete the operation due to error 8007000e.
“Not enough storage is available to complete this operation”
I don't get such errors with other browsers.
Why does it happen ?
I use IE 11. Windows 8.1 64bit 16GB RAM
I had a similar problem with one of applications. The same stuff worked well in Firefox and Chrome. In my case IE failed when it consumed more than 1.2 GB memory. I also noticed memory management was better in Firefox and Chrome and it stayed less than 800M all the time.
If you have a similar situation you can capture memory footprints from IE and other Browser using developer tools to get further clue. In my case problem was due to a third party component application used.
It looks like you've reached the quota for your local browser storage. Here's a link you can refer to see the various storage limitations of each browser.
http://www.html5rocks.com/en/tutorials/offline/quota-research/
If pulling the request.reponseText doesn't throw the error itself (without the JSON.parse-ing), try to consider storing it in an IndexedDB. As per the link above, IE11 can hold from 100MB of data
Steps on how to create one can be found here:
http://msdn.microsoft.com/en-us/library/ie/jj154905(v=vs.85).aspx
http://hacks.mozilla.org/2012/02/storing-images-and-files-in-indexeddb/
i just ran into a problem with my node webkit app using express framework.
Situation:
I successfully built the app with ~ 150mb, including some dummy data. I'm zipping the whole project and rename it to .nw according to the instructions readme. Everything is working fine.
BUT:
When adding the actual content to the app, the app size grows up to 3.8gb. It seems that my windows machine (4GB RAM / 32bit windows 7) can't start the app. I've waited almost an hour - several times, but still nothing happens - no error message, no hourglass cursor - just nothing.
Does anyone know of any limitation regarding node app size which could possibly cause this "misbehaviour"? It runs flawlessly on my mac with 8GB RAM, so i guess there's the rub...
If you could just help me, that'd be great,
thanks in advance!
This article should explain part of your problem: http://en.wikipedia.org/wiki/3_GB_barrier
The other part of your problem: Are you sure you need to load all 3.8GB of that application at once? There are relatively few applications where that would be a hard requirement. Is there a part of your application that you could refactor in order to have a much smaller portion in memory at any single time?
I have a joomla website hosted on one of my LAMP servers. Somehow joomla is "eating" up drive space and i am constantly receiving the error: "This domains disk limit has been exceeded!"
I tried to increase the disk limit(i use ZPanel) and it worked, but after a few days it went to this error-screen again.
I would appreciate any help. Thanks.
Check your files.
see how /images/ evolved over time (it really depends on how much content you upload) or any other components that create content
examine /tmp/ and empty it
check /cache/ folder
Joomla! core files don't usually grow over time in a significant way.
I have a cocoa app which uses core data. Everything seems to be working fine.
However, in a very specific scenario the app was behaving very strangely for our client.
In particular the logs shows this appearing in the output many times (which I've never seen in my testing):
Core Data: annotation: -executeRequest: encountered exception = Updating max pk failed: with userInfo = {
NSSQLiteErrorDomain = 14;
}
Has anyone ever seen this message and do you know what it means? I've tried googling it but found no information other than a few message boards regarding the Growl app having similar problems, with no solution yet available.
Sorry that I can't be more specific regarding what causes this as I'm not even sure myself. I know how to reproduce this on the client's machine but this message seems very random.
I was hoping someone could give me some more information as to what this error means exactly so that I can maybe narrow it down some more. Right now I'm pretty clueless.
Note: This appears on a macbook pro running 10.7.2 (if that matters).
Thanks for any kind of help you can provide, even something vague would help me at this point.
Update:
The managed context "save" method also fails with the following error:
The operation couldn’t be completed. (Cocoa error 134030.)
This is not really a Core Data problem as such, but more an issue of you process running out of file descriptors.
Each process has a limited number of file descriptors. If you run out, Core Data (and many other things) will stop working, because they can no longer open files -- any they'll fail.
First of all, make sure you're not leaking file descriptors, i.e. make sure you close files when you no longer need them.
I'm not sure what kind of changes you're trying to track. Take a look at Tracking File-System Changes.
If you're on 10.7, take a look at dispatch sources and DISPATCH_SOURCE_TYPE_VNODE for a very powerful tool to track file system changes (corresponds to kqueue, but is easier to use).
Core Data also gives this error in a Sandboxed app when it tries to save DB to a location where it doesn't have full read/write access to (if a user opens file for example, Core Data will be able to read/write this file, but not anything else to the same folder).
Core Data fails to write the temporary _journal file to this folder and reports this error.