#330 closed defect (fixed)
TB 5 freeze on new mail for "storing virtual identity"
Reported by: | Owned by: | ||
---|---|---|---|
Version: | 0.8.0 | Keywords: | |
Cc: |
Description
When I create a new email, Thunderbird 5 will freeze for about 20 seconds and in the status bar shows the message "storing virtual identity". Then the message disappears and I can go back to using the cursor. This problem was not with earlier versions. You can control it?
Change History (5)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
Same problem here on 2 differents computers one on WinXP32 the other Win7 64 running Thunderbird 32. was ok with previous TB/VI When opening new message freeze for 5 to 10 sec (sometime thunderbird pop up with that script take too long ) when first clic on subject freeze again for 5 sec when clic on message freeze 5 more sec
The first slowdown (new message->freeze) appears after
## v_identity: mod. FillIdentityList
Then the Log is errased and replaced by that
Thunderbird 5.0 (20110624125636; Windows NT 6.1; WOW64) -------------------------------------------------------------------------------- ## v_identity: composeDialog reopened. (msgType 0) ** v_identity.xml identityData setter ** v_identity.xml identityData setter done.' ## v_identity: everything cleaned. ## v_identity: initSystemStage1. ** v_identity.xml identityData setter ** v_identity.xml smtp set to '' ** v_identity.xml resultingID: fullName='MeMeMe' email='Me@Me.Me' smtp='vI_useDefaultSMTP' id='id1' existingID='true' ** v_identity.xml identityData setter done.' ## v_identity: initSystemStage2. ## vI_smartIdentity: msgComposeType = 0 ## vI_smartIdentity: checking against id1 ## vI_storage: getVIdentityFromAllRecipients() ## vI_storage: _walkTroughCards searchUri='moz-abmdbdirectory://abook.mab?(or(DisplayName,c,))' ## vI_storage: _walkTroughCards searchUri='moz-abmdbdirectory://history.mab?(or(DisplayName,c,))' ## vI_storage: _walkTroughCards searchUri='moz-abldapdirectory://ldap_2.servers.Myserver_1?(or(DisplayName,c,))' ## vI_storage: isMailingList false ## vI_rdfDatasource: _getRDFResourceForVIdentity: no Recipient given. ## vI_rdfDatasource: findMatchingFilter for . ## vI_rdfDatasource: findMatchingFilter no match found. ## vI_storage: found 0 address(es) ## v_identity: reopen done. addon: Virtual Identity 0.8.0 addon: Default 5.0 addon: Foxit Reader Plugin for Mozilla 1.0.1.1117 [DISABLED] addon: Google Update 1.3.21.57 [DISABLED] addon: Shockwave Flash 10.3.181.26 [DISABLED] addon: Java(TM) Platform SE 6 U22 6.0.220.4 [DISABLED] addon: Java Deployment Toolkit 6.0.220.4 6.0.220.4 [DISABLED] addon: Silverlight Plug-In 4.0.60531.0 [DISABLED] addon: Microsoft Office 2010 14.0.4730.1010 [DISABLED] addon: Microsoft Office 2010 14.0.4761.1000 [DISABLED] addon: NVIDIA 3D Vision 7.17.12.6717 [DISABLED] addon: NVIDIA 3D VISION 7.17.12.6717 [DISABLED] ## vI_storage: awOnBlur 'addressCol2#1' ## vI_storage: updateVIdentityFromStorage() ## vI_storage: no recipient found, not checked.
It could help if Log was timestamped and not replaced by another one.
After reading the Log I find the Problem it's The LDAP server. If I Removed the LDAP from my address book it works fine as before. It would be nice not to search on LDAP for Identity, or have an option.
Best Regards
comment:3 Changed 11 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Hi,
it's hopefully already fixed as a reaction to #325 with commit [d28e7866fa]. Please check the snapshot at http://absorb.it/software/virtual_identity/other/virtual_identity-0.8.0-7-g0a199fa-tb+sm.xpi which prevents checking remote address-books.
Please reopen the ticket if this does not fix your problems.
Regards, Rene
comment:5 Changed 11 years ago by
But after restart again problem: 5 secondes freeze. I have erased Ldap server, present but inactive, and problem solved.
Hi,
if you store some identity, the data will be stored in your profiles folder. If this is hardly accessible (on some remote machine) there might be a reason why this takes that long. It shouldn't otherwise.
To debug the case please check the error console and enable the debug-log to see when it exactly stops.
Nice Regards, Rene