Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.2.0f3
Issue ID
960031
Regression
No
Collab: revisions?include=changes call is uncompressed and can get really large (4+ megabytes
The call to revisions?include=changes (to show the history window) can get ridiculously large when there are a large number of files in the changes retrieved. For example, when retrieving the most recent changes for a project where I published 20,000 unique randomly-generated text files, the call resulted in a response body >4 megabytes.
REPRO STEPS:
1. Start Fiddler / Charles Proxy
2. Create a project and enable collab
3. Publish 20,000 files
4. Using Fiddler / Charles, look at the size of the response for revisions?include=changes when refreshing the Collab History window
RESULTS:
revisions?include=changes call is >4MB and uncompressed
EXPECTED:
Large calls that are mostly text are GZIPped
IMPACT:
Major slow-down for users retrieving collab history at average connection speeds
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Destroying assets is not permitted to avoid data loss” error thrown when creating a second Tile Palette Brush Pick Asset
- The “Copy to clipboard” button has no hover or click animations when hovering and clicking the “Copy to clipboard” button after selecting an issue from the “Code” tab of the Project Auditor window
- Saved Tile Palette Brush List items become malformed causing the list to become cut off when decreasing the Pick size with the slider
- Foldout triangle icons and the foldouts titles are not aligned/centered in the “Assembly” and “Areas” Filter windows of the Project Auditor window
- High MeshSkinning duration when using Vulkan
Add comment