[COMPASS-4141] compass-crud: initial load when loading large documents runs out of RAM Created: 12/Feb/20 Updated: 10/Jan/24 Resolved: 03/May/21 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | CRUD |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Irina Shestak (Inactive) | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Documentation Changes: | Not Needed |
| Description |
|
Seems like with documents over a particular size, electron runs out of RAM even with allowDiskUse:true flag. Issue originally reported on github – https://github.com/mongodb-js/compass/issues/1894 Description from github: As for Aggregate tab - this is where it is not usable as the tab will not render any content into itself - e.g. it will be empty so a client of mongodb UI can't use this tab at all - I can't change the filter/aggregate etc Detailed Description Context I'm using Windows version of MongoDB Compass Comunity UI version 1.20.3" |
| Comments |
| Comment by Maurizio Casimirri [ 03/May/21 ] |
|
This seems to be working as expected. The user gets an error from server and has to create a projection to exclude any problematic fields. claudia.deangelis I'm going to close this, but would they asked to show a list of documents anyway, could it be that our "error message banner" is not visible enough and the user was thinking that the collection is empty instead? |