Closed Bug 512050 Opened 15 years ago Closed 14 years ago

Application hang

Categories

(Toolkit :: Application Update, defect)

x86
Windows Vista
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: vefil, Unassigned)

Details

(Keywords: hang, Whiteboard: [support])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; fr; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)
Build Identifier: 

the application "gèle"... since the last update of august 12 th... i use vista...
;-(

Reproducible: Always
Reporter what version of TB you use?

The application freeze\hang at the startup?

Can you try in safe-mode?
Summary: l'appliation gèle → Application hang
Whiteboard: [support]
the last updating was next week that means I use the latest version version 2.0.0.23 (20090812)

when I read a mail it takes very long to charge, then do destroy ou answer the mail, almost each time I get the message thunderbird doesn't respond.
Never happen before.


what do you mean by safe-mode ? 
forgive my english which is quite.... uneasy.
My english isn't better of your ;-)

On start-->All programs (at least in Windows XP), search Mozilla Thunderbird folder: into this folder there is a link to "thunderbird (safe mode)".

Otherwise, add to launch to Thunderbird in your taskbar or desktop  -safe-mode (with space first).
Thanks I found the link... I will try for a few days... until there is a new update avalaible... thank you again.
Severity: normal → critical
Component: General → Application Update
Keywords: hang
Product: Thunderbird → Toolkit
QA Contact: general → application.update
Please attach the last-update.log along with updates.xml as mentioned in Comment 2. Without that file we won't be able to go any further.
Please ignore previous comments. Please update if you are able to still reproduce the application hand. Have you tried in safe-mode ?
No response to comment #6. Resolving -> incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.