"Bad VM cache data" message behavior takes hours
Bug #1218503 reported by
Mark Diekhans
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
VM |
Triaged
|
High
|
Uday Reddy |
Bug Description
I was wanted to experiment with the trunk VM. When visiting a mailbox created with 8.2.0b, I get one
:Bad VM cache data: ...": per message.
This is simple because the vector needs to be longer
This is very alarming to see and one doesn't realizes it's not corruption until reading the code. It's at
the most severe warn level and then it waits 2 second per message. I have mail boxes that would take hours
to convert with the 2 second wait.
If the mailbox is read-only, this happens every time the box is visited.
Suggest that the text of the message be made less alarming and that the level be change do it doesn't
show up by default.
Changed in vm: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Uday Reddy (reddyuday) |
milestone: | none → 8.2.0b1 |
tags: | added: compatibility new |
tags: | removed: compatibility |
Changed in vm: | |
milestone: | 8.2.1a → 8.2.0 |
Changed in vm: | |
milestone: | 8.2.1a → 8.2.0 |
Changed in vm: | |
milestone: | 8.2.0 → 8.2.90a |
Changed in vm: | |
milestone: | 8.2.90a → 8.3.0 |
To post a comment you must log in.
Apparenty, this also happens when upgrading from 8.1.2 to 8.2.0b. It needs to be painless.