[Dev Server] Large image uploads reduced permanently to thumbnails + Dynamic Lighting layer issues

Setup Information: Firefox 65.0.2 (most recent stable release) Chrome 72.0.3626.121 (Official Build) OS: Windows 7 Home Premium 64-Bit Javascript Enabled Antivirus (Malwarebytes) disabled completely during testing All add-ons and extensions disabled during testing Problem persists in inPrivate/Incognito mode. Problem persists after cache cleared.Problem persists in both browsers. Problem No. 1: Large image uploads Images with a large resolution (see resources below) successfully upload, but throw several errors in the console, and the image uploaded to the Library is an extremely low-res version. Additionally, images previously uploaded (&gt;2 weeks ago) over a certain size have also been reduced to thumbnails. I have not yet determined the exact resolution necessary to reproduce this. I am able to reproduce this issue 100% of the time with the images that originally had this problem. Relatedly, I was unable to select the compromised image by clicking it, and instead had to either drag an area over it or select-all with CTRL-A. Small-resolution images are unaffected. Steps to Reproduce: Attempt to upload the following image by dragging the image onto the canvas OR uploading through the Upload Files dialog: Console Output (Firefox): &nbsp;app.js:547:30640 DROP ON FILE UPLOAD app.js:553:1646 Not Video; sizeArray: Array(5) [ (3) […], (3) […], (3) […], (3) […], (3) […] ] app.js:552:27652 Reader load! app.js:552:27792 zombie wizard basement dungeon.png app.js:553:504 89774546 app.js:553:568 Uploading a size: 100x100 app.js:552:28047 Uploading a size: 200x200 app.js:552:28047 XML Parsing Error: no root element found Location: <a href="https://s3.amazonaws.com/files.d20.io/images/76070897/BKoYKI_uFWCkN1xnEb_TOw/mini.png?AWSAccessKeyId=AKIAIVMOBMWG4CULMUMQ&amp;Expires=1552239208&amp;Signature=kc0XbMYBijb5fgCyn7nUBauJFdw%3D" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/76070897/BKoYKI_uFWCkN1xnEb_TOw/mini.png?AWSAccessKeyId=AKIAIVMOBMWG4CULMUMQ&amp;Expires=1552239208&amp;Signature=kc0XbMYBijb5fgCyn7nUBauJFdw%3D</a> Line Number 1, Column 1: mini.png:1:1 Uploading a size: 512x512 app.js:552:28047 XML Parsing Error: no root element found Location: <a href="https://s3.amazonaws.com/files.d20.io/images/76070897/BKoYKI_uFWCkN1xnEb_TOw/thumb.png?AWSAccessKeyId=AKIAIVMOBMWG4CULMUMQ&amp;Expires=1552239209&amp;Signature=CeZRLL0l3uLBIL4I%2BHUyu8PrAPA%3D" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/76070897/BKoYKI_uFWCkN1xnEb_TOw/thumb.png?AWSAccessKeyId=AKIAIVMOBMWG4CULMUMQ&amp;Expires=1552239209&amp;Signature=CeZRLL0l3uLBIL4I%2BHUyu8PrAPA%3D</a> Line Number 1, Column 1: thumb.png:1:1 Uploading a size: 2048x2048 app.js:552:28047 XML Parsing Error: no root element found Location: <a href="https://s3.amazonaws.com/files.d20.io/images/76070897/BKoYKI_uFWCkN1xnEb_TOw/med.png?AWSAccessKeyId=AKIAIVMOBMWG4CULMUMQ&amp;Expires=1552239209&amp;Signature=By9HHJ9bkO6mIQJDdylhnb%2BvPBQ%3D" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/76070897/BKoYKI_uFWCkN1xnEb_TOw/med.png?AWSAccessKeyId=AKIAIVMOBMWG4CULMUMQ&amp;Expires=1552239209&amp;Signature=By9HHJ9bkO6mIQJDdylhnb%2BvPBQ%3D</a> Line Number 1, Column 1: med.png:1:1 Uploading a size: 10000x10000 app.js:552:28047 XML Parsing Error: no root element found Location: <a href="https://s3.amazonaws.com/files.d20.io/images/76070897/BKoYKI_uFWCkN1xnEb_TOw/max.png?AWSAccessKeyId=AKIAIVMOBMWG4CULMUMQ&amp;Expires=1552239210&amp;Signature=mtRzG3by9YV%2FVP19LzYMiNpRApw%3D" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/76070897/BKoYKI_uFWCkN1xnEb_TOw/max.png?AWSAccessKeyId=AKIAIVMOBMWG4CULMUMQ&amp;Expires=1552239210&amp;Signature=mtRzG3by9YV%2FVP19LzYMiNpRApw%3D</a> Line Number 1, Column 1: max.png:1:1 XML Parsing Error: no root element found Location: <a href="https://s3.amazonaws.com/files.d20.io/images/76070897/BKoYKI_uFWCkN1xnEb_TOw/original.png?AWSAccessKeyId=AKIAIVMOBMWG4CULMUMQ&amp;Expires=1552239212&amp;Signature=nI8JIb6yHZ0mdZH0jRNiIIF92dA%3D" rel="nofollow">https://s3.amazonaws.com/files.d20.io/images/76070897/BKoYKI_uFWCkN1xnEb_TOw/original.png?AWSAccessKeyId=AKIAIVMOBMWG4CULMUMQ&amp;Expires=1552239212&amp;Signature=nI8JIb6yHZ0mdZH0jRNiIIF92dA%3D</a> Line Number 1, Column 1: Image appears as follows: Small images, such as this one, are unaffected: Problem No. 2: Dynamic Lighting Drawing Object Weirdness I'm not sure if this issue is related to the previous one, and have not been able to reproduce it. Both of these issues affected the 'Lamella's Basement' page of this campaign: <a href="https://app.roll20dev.net/campaigns/details/46121/deans-5e-table" rel="nofollow">https://app.roll20dev.net/campaigns/details/46121/deans-5e-table</a> I use the Walls API script to generate dynamic lighting objects for my maps. It works excellently, and this report is unrelated to that script. The lighting objects present on the page had two kinds: Long, red segments with transparent fills for the walls, and short, green segments with transparent fills for the doors. When I went to load my table to run my weekly game for my players, this is what I saw on my dynamic lighting layer: Apparently, all of the dynamic lighting objects had been: 1. Entangled badly. 2. Moved out of position. 3. Changed to white lines with a black fill. 4. Merged together into seemingly-random clumps. I was able to select the objects, but only by selecting all with CTRL-A. Here is what the objects look like when reverted to red lines with a transparent fill: I'm unsure if this is related to the issue where the user is unable to access their library or upload new assets unless logged into roll20.net in the same browsing session as the roll20dev.net/editor tab. If that hasn't been reported already (I assume it has) I'll make a separate report for that at a later time.

Hello&nbsp;Doonthelis, Thank you for providing us these details. i have passed along this information to our devs. We hope to have an answer for you soon.

Hi Drespar, I'm glad to hear that the critical issue is being worked on! The clumping occurred on a page created after creating the campaign on the dev server - it wasn't a transfer from production. I had not touched that page for about two weeks after preparing it for use - I loaded up my table and summoned my players, only to find everything was broken! I haven't been able to force it to do it again on any other page, so far, either.

This issue appears to have been resolved, on my end. Roll20 staff, feel free to close this thread at your leisure. Thank you to the Roll20 Team for responding and fixing the issue within such a short time frame.