global search index file size of imap inbox

RESOLVED WORKSFORME

Status

Thunderbird
Search
RESOLVED WORKSFORME
5 years ago
5 years ago

People

(Reporter: nihaopaul, Unassigned)

Tracking

({perf, regression})

17 Branch
x86
Mac OS X
perf, regression

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 675798 [details]
Screen Shot 2012-10-27 at 12.01.00 PM.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Firefox/17.0
Build ID: 20121023124120

Steps to reproduce:

upgraded tb 17


Actual results:

INBOX of imap account grew to unreasonable size


Expected results:

remain constant, disabling global search index and compacting the folder fixed this issue, one machine grew to 29gb the other machine grew over 50gb before running out of space, one was stable in ubuntu, the other was pre-release on osx

Comment 1

5 years ago
Please check the files in the account directories of fhe thunderbird profile.   Are any are larger than they should be?
Keywords: perf, regression
xref bug 803843

Comment 3

5 years ago
nihaopaul, is tb17 beta 2 better?

(In reply to Wayne Mery (:wsmwk) from comment #1)
> Please check the files in the account directories of fhe thunderbird
> profile.   Are any are larger than they should be?

yeah, that was a dumb question.
Flags: needinfo?(nihaopaul)
(Reporter)

Comment 4

5 years ago
testing now with the latest nightly, so far it's not grown but i've only just turnt it on
Flags: needinfo?(nihaopaul)

Comment 5

5 years ago
(In reply to nihaopaul from comment #4)
> testing now with the latest nightly, so far it's not grown but i've only
> just turnt it on

nihaopaul, still good?
if yes,  please set status to RESOLVED and resolution to WORKSFORME
Flags: needinfo?(nihaopaul)
(Reporter)

Comment 6

5 years ago
thanks for the Prod, i can confirm it's resolved!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 5 years ago
Flags: needinfo?(nihaopaul)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.