[Bug] Database error from no disk space #854

New Issue

MrUnknownDE · 2026-04-05T16:29:52+02:00

MrUnknownDE commented

2026-04-05 16:29:52 +02:00

Originally created by @TheXev on 5/15/2024

Describe the bug
VRCX reports that my Database as failed to upgrade after most recent public build installation.

To Reproduce
Steps to reproduce the behavior:

Open VRCX
Warning message appears stating not to close VRCX, Database update in progress
Database update fails and an debug dialog appears

Expected behavior
VRCX opens and updates database.

Screenshots

What version you are running
Version 2024.05.09

I would like to note that my database is close to 4 years old now and I have intentionally made it larger. I do not know if it's sheer size is becoming a problem.

edit This bug is mostly erroneous and I apologize for opening it. I turns out I was out of disk space and had no idea. Update worked after cleaning up my drive space.

However, it might be a wise idea to examine this scenario and have VRCX produce a more human readable error message about needing more drive space to migrate the database.

*Originally created by @TheXev on 5/15/2024* **Describe the bug** VRCX reports that my Database as failed to upgrade after most recent public build installation. **To Reproduce** Steps to reproduce the behavior: 1. Open VRCX 2. Warning message appears stating not to close VRCX, Database update in progress 3. Database update fails and an debug dialog appears **Expected behavior** VRCX opens and updates database. **Screenshots** ![image](https://github.com/vrcx-team/VRCX/assets/5352607/9d061075-689b-4468-8c38-9ae851687a1d) **What version you are running** Version 2024.05.09 I would like to note that my database is close to 4 years old now and I have intentionally made it larger. I do not know if it's sheer size is becoming a problem. *edit* This bug is mostly erroneous and I apologize for opening it. I turns out I was out of disk space and had no idea. Update worked after cleaning up my drive space. However, it might be a wise idea to examine this scenario and have VRCX produce a more human readable error message about needing more drive space to migrate the database.

MrUnknownDE closed this issue

2026-04-05 16:29:52 +02:00

Sign in to join this conversation.

No Label Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug Bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/VRCX#854