I am unable to upload a screenshot to my chrome extension dashboard in Web Store. Everytime I upload any image, an error prompts 'Image size is incorrect'.
I have tried every possible way to tackle this -
1] Uploaded the correct pixel dimension (1200800 or 600400 JPEFG or 24 bit png)
2] Compressed the screenshot in order to reduce the size of the file (I thought maybe 'incorrect size' refers to the file size)
Related
Current Network Devtools tab displays MBs:
Is there some settings to display MBs in KBs and in full number, not decimal (33.5 as 33500)? Need to know precise value (e.g. 33.5 => 33527)
I don't think there is a way to change the unit used by the Size column, but you can do one of the following:
download the file and inspect its size locally
add a column for a 'Content-Length' response header
As you can see on the screenshot it's not perfect though - it's provided by the server and it's not required.
export entry as a HAR file and look up the exact value
use the Resource Timing API to list all resources in the console
(see Possible to list external resources loaded on a webpage with JavaScript? )
I'm getting an error in Chrome for an offline web app. Google Chrome always fails on the third video, despite the URL being correct and clicking on the URL in the Google Dev Tools' error message, opens and plays the video in a new tab. (It's always the third, even if I change the order of the videos)
The manifest has three videos (each 30-40 MB). All three can be viewed in chrome and are listed in the manifest. It shows a message that it's downloaded the first two videos but the third always ends in this message:
Application Cache Error event: Resource fetch failed (2) myvideo3.mp4
I know the manifest is correct because (as mentioned), clicking on the URL in the error message plays the video in a Chrome tab.
Since it always fails on the 3rd video despite changing the order in the manifest, I believe it's a limit on app cache size. How do I increase this for my app? This is a desktop.
CACHE MANIFEST
CACHE:
test.php
image.png
videos/myvideo1.mp4
videos/myvideo2.mp4
videos/myvideo3.mp4
EDIT: Some more info:
When I have three videos listed, it loads two and fails on the thrird. BUT, when I take the third off and only have two listed in the manifest, it fails on the 2nd video! What could cause this? (If I have only one video, then it loads that one and the whole manifest)
Using:
Google Chrome 43 on Desktop (64-bit)
There's not just a per-web-app size limit, but also a per-file size limit. From this post (and confirmed by my testing), it's 32mb per file and 260 MB per web app.
Not sure how to find out the limit on other browsers as this seems to be undocumented.
If I understand this API documentation correctly: https://developer.chrome.com/apps/offline_storage
...
Then it is saying Application Cache is part of Temporary Storage where you cannot ask for more space and you get a maximum of 20% of the pool.
navigator.webkitTemporaryStorage.queryUsageAndQuota (
function(usedBytes, grantedBytes) {
console.log('we are using ', usedBytes, ' of ', grantedBytes, 'bytes');
},
function(e) { console.log('Error', e); }
);
This function told me I have 100MB of granted space. So I assume my app has 20MB? How do I know how much each individual file can be?
I don't know about the limits mentioned in the post above, they seem to be referencing an old answer.
I have a "JSFiddle-like" demo of fetching PNG (Binary Blobs) in a tight loop using XHR2. This first demo grabs 341 PNG images, and then saves them in IndexedDB (using PouchDB).
This demo works fine: http://codepen.io/DrYSG/pen/hpqoD
(To operate, first press [Delete DB], Reload Page, wait for Status = Ready (you should see that it plans to fetch 341 tiles), then press [Download tiles]. )
The next demo is the same code (identical JS, CSS, HTML), but it tries to get 6163 PNG files (again from Google Drive). This time you will see many XHR 0 errors in the console log.
http://codepen.io/DrYSG/pen/qCGxi
The Algorithm it uses is as follows:
Test for presence of XHR2, IndexedDB, and Chrome (which does not have binary blobs, but Base64). and show this status info
Fetch a JSON manifest of PNG tiles from GoogleDrive (I have 171 PNG tiles, each 256x256 in size). The manifest lists their names and sizes.
Store the JSON manifest in the DB
MVVM and UI controls are from KendoUI (This time I did not use their superb grid control, since I wanted to explore CSS3 Grid Styling).
I am using the nightly build of PouchDB
All files PNG file are feteched from Google Drive (NASA Blue Marble.
I created the tile pyramid with Safe FME 2013 Desktop.
My guess is what is happening is that all these XHR2 requests are being fired async, being placed on a thread separate from the JavaScript thread, and then when there are too many pending requests, Chrome is getting sick.
FireFox does not have this issue, nor does IE10.
You can fork the code, and try different values for line 10: (max number of tiles to fetch).
I have submitted a bug to Chromium Bugs, but does anyone have any experience in throttling the async XHR2 fetches for large downloads of data to the Chrome Browsers?
The chromium folks acknowledge this is something that they should fix: https://code.google.com/p/chromium/issues/detail?id=244910, but in the meantime I have implemented throttling using jquery defer/resolve to keep the number of threads low.
Update: I am going to delete my codepen, since I don't need to show this error anymore.
STEPS TO REPRODUCE THE PROBLEM:
Step 1: Let´s say you have cleaned up your cache history on your browser (firefox).
Step 2: You type www.stackoverflow.com on your browser to could get some new data on your cache folder.
Step 3: you type on your browser "cache:about"
Step 4: you click on "Disk cache device/List cache entries"
Step 5: I search for some ".png" file that has been downloaded to my cache folder. And taking notice that the data size is actually 16425bytes.
Step 6: Copy the path where the image has been stored on your computer.
Step 7: I take a fast look how the image looks like by clicking on this link before I continue with the problematic issue.
Step 8: Checking image
Step 9: Start/run/ and pasting the path we have copied recently, where the image has been stored on your system.
Step 10: Here is the image! But we have to type manually ".png"
Step 11: I take a look how it looks like:
Step 12: I edit the image I want to change the size of the file and have another size than the real one that the browser cached. So I make the image smaller and save it.
Step 13: I check so the size of the file have really changed.
before was 17kb now 3kb.
Step 14: I remove the ".png" text i added to the file name so the browser can read it
Step 15: Now I press reload on my browser and the file don´t gets readed!
EXPECTED RESULT:
- On the example to make it simple to understand I used a ".png" but you don´t get the same result. On my real issue amb trying to make the cache read a FLASH .swf file that I hade change it activly the original data size..
Any ideas? links? I can´t find info on internet about how to say to the browser to read again the file that has been downloaded, even if the size has changed!!
The point is that client will never check the server again if it is cached, until (and if) the cache has expired for that element. Set a max age on the HTTP header to 10 minutes say, for client to redownload it if it has been more than 10 mins since last downloaded. You cannot update just because size changed. Unless you have a JS or ajax or something that will update the client cache based on some result that is retrieved when the client checks the server to see if there was a recent change, other that it is impossible.
So if you have to have it, you will have to keep track on the server if something changes, based on existing data on the server. For instance, server keeps track of the initial size. If you change the image size (or suppose something in your web application changes it), the server will know that this has been changed on the server (because it will always get the current image size too on the server). So then you also need to keep track of the image size on the client when the image is downloaded, with either a cookie or with html5 localStorage.
So then the client part of your script requests the server on page load (sending the image size too that is stored in cookie or localStorage) and the server script will then compare the size of current image with the size sent by the client. If it is different it expires the client cache explicitly which means the client has to redownload the image explicitly. Otherwise it does nothing and just uses the cached image.
So basically you will need to treat your image much like you would a login cookiet(where server explicitly tracks it, expires it, sets new one, expires it, etc.) if you want this kind of functionality.
i was facing the same problem, finally got a work around, thanks to this thread.
this is for firefox only.
goto about:config
edit the variable "browser.cache.check_doc_frequency" (default 3) to 2
(http://kb.mozillazine.org/Browser.cache.check_doc_frequency)
edit the file in the cache directory. (doesn't matter if the new size is different!)
no need to change the file size entries in chache_001.
hope this helps you.
Edit: just make sure you keep the file size less than the original one for swf files.
Reason: I don't really know, but when I tried editing a swf for an online game, the game could no longer load with the new cache file (like firefox reserves x memory bytes for the thing, x was specified by the server .. but the file is larger than x bytes, so the whole file will not be loaded, and the flash movie wont load).
I edited some of the images in the swf to blank images of the same size, recompiled and recompressed to get a filesize lower than that of the original swf, and it worked!
I know that IE & FF don't support file uploads larger than 2 GB. But can we somehow get to know that browser did not send request for a file larger than 2 GB?
I am using GWT upload panel. When we attach a file larger than 2 GB and submit the form,IE fires onSubmitComplete even but event.getResults() is null. event.getResults() is also null when internet disconnects.
Firefox does on even fire this event.
Is it possible to detect (at client side via some event or error) that upload has failed due to size limit?
Regards,
Nadeem Ullah
Why don't you check the file size before trying to upload it? If it's greater than 2GB, send a warning to the user ...