- Newest
- Most votes
- Most comments
I apologize to hear that you're experiencing crashes and white screen issues with AWS NoSQL Workbench. While the tool is indeed powerful for designing and working with DynamoDB, occasional stability issues can occur.
Since you've mentioned that you're using the latest version (3.13.3), which was released quite recently, it's possible that there might be some bugs that haven't been fully addressed yet. Here are a few suggestions that might help:
-
Ensure your system meets the minimum requirements for running NoSQL Workbench.
-
Try uninstalling and reinstalling the application to rule out any installation-related issues.
-
If you're working with large datasets or complex operations, try breaking them down into smaller chunks to reduce the load on the application.
-
Check if the issue persists when working with smaller tables or simpler operations.
-
Make sure you're running the latest version of your operating system and that all system updates are installed.
-
If possible, try running NoSQL Workbench on a different machine to see if the issue is specific to your current setup.
If the problem continues, it would be beneficial to report this issue to AWS support or through the AWS forums. Provide details about your system configuration, the specific actions that lead to the crash, and any error messages you might see. This will help the development team investigate and potentially address the issue in future updates.
In the meantime, to mitigate data loss, consider saving your work frequently and, if possible, backing up your data models and operations regularly.
Sources
NoSQL Workbench for Amazon DynamoDB - A professional GUI client
Exploring datasets and building operations with NoSQL Workbench - Amazon DynamoDB
NoSQL Workbench for DynamoDB - Amazon DynamoDB
Hello, can you provide us a screencasts or any error logs of what you are seeing? Our NoSQL Workbench team is trying to reproduce this issue. Can you link us to a screencast or error log file? Feel free to provide us a link where we can access this or directly email us through the NoSQL Workbench app by clicking "Share feedback"
accidentally added an "answer" as a reply to the thread instead of commenting here.
The other way I have replicated this has been to be editting the table data through the workbench for more than 30 seconds or by doing it too quickly. I have been modifying the data in the json file and reuploading every time instead.
Relevant content
- asked 5 months ago
I just happened to figure out that clicking the 'Clear application state' button generates the exact same white screen but that there is no way to get back from said white screen without closing and reopening. Now I am not accidentally clicking that button to get to the white screen while I am editing data rows, but still interesting that such a button exists.
Further the memory keeps spiking for the application in the task manager view. I would go to edit a data row and type some random letters quickly and watch the memory spike up an additional 600MB and then not come back down at all. During this it would get super slow and freeze up.
Further, I have uninstalled and reinstalled. I have ran as administrator. I have restarted my desktop. I only have ~20 datarows. This should be a super small amount of data.