Closed Bug 414350 Opened 17 years ago Closed 16 years ago

Thunderbird crashes on startup when network-based profile is used

Categories

(Thunderbird :: General, defect)

Product:
Thunderbird
Component:
General
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: zaphod, Unassigned)

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 Build Identifier: 2.0.0.9 (20071031) When using a network-based profile on a Mac OS 10.5 hosted AFP share, Thunderbird crashes on startup under Mac OS 10.5 (Leopard) Reproducible: Always Steps to Reproduce: 1. Start Thunderbird under Mac OS 10.5 with profilemanager option 2. Specify remote AFP directory on Mac OS 10.5 server as profile location 3. Start Thunderbird Actual Results: Thunderbird crashes on startup Expected Results: Thunderbird works with network-based profile - When started with command line in terminal, on startup error message "segmentation fault" is given (not every time)
Give the crash talkback id, if you get one. http://kb.mozillazine.org/Talkback
Talkback is properly installed and enabled. Talkback is not started automatically at crash time, though, and in the list of Talkback Incidents (when starting Talkback manually after the crashes) there are no incidents listed. Crashes happen < 0,5 sec after program start.
in that case, you might try a trunk build in hopes that it kicks one out with the new crash reporter
Keywords: crash
- Tried Thunderbird version 3.0a1pre (2008021503). Problem persists. - Meanwhile updated server and client to Mac OS 10.5.2. Problem persists. - Crash reporter of Tbird v3.0a1pre does not report anything at crash time. - Manual start of Crashreporter.app results in crash of the crash reporter... - Tbird 3.0a1pre works fine with a local profile.
Christian, please have a look if you can find following file on your system: ~/Library/Logs/CrashReporter/thunderbird-bin.crash.log
@ Henrik: In the directory specified by you, there is no crash log from Thunderbird. In addition, when crashing, the obligatory Mac OS message "The application ... crashed unexpectedly..." is not given. When started with the network profile, the Tbird crash occurs silently within 0,5 sec with the sporadic error message "Segmentation fault" if the application is started from the terminal. More observations: - On the remote profile directory, some profile data are written prior to the crash - sometimes more, sometimes less. - If the profile is stored locally but the individual mailboxes are stored remotely, it works (our current setup) - If hosted on a Mac OS 10.5 server system, but connected via SMB protocol, Tbird does not crash on initial startup (profile data are created ok) but is unusable due to recurrent hangs. - If hosted on a Mac OS 10.1 server system, Tbird network profiles via AFP work flawlessly.
Thanks Christian. I'll have a look at it within the next days. I got a new Mac Mini with Leopard today and have to setup it first. As soon as I'm able to have my first debug builds available I'll have a test via AFP protocol. Meanwhile could you run a test with a trunk build of Thunderbird and a test profile? Does it also happen there? ftp://ftp.mozilla.org/pub/thunderbird/nightly/latest-trunk/
(In reply to comment #7) > Meanwhile could you run a test with a trunk build of Thunderbird and a test > profile? Does it also happen there? Henrik, please have a look at comment #4 of this bug report. There you will find my experiences with a trunk build. Thanks for your efforts!
(In reply to comment #4) > - Tried Thunderbird version 3.0a1pre (2008021503). Problem persists. > > - Meanwhile updated server and client to Mac OS 10.5.2. Problem persists. > > - Crash reporter of Tbird v3.0a1pre does not report anything at crash time. > > - Manual start of Crashreporter.app results in crash of the crash reporter... Ted, What's needed for a bug report on the last item? (I didn't find any) What to do about lack of stack?
You can file it, but it's not going to get anywhere without some more info. An Apple crash reporter stack from the crash, or using gdb to get a stack would help.
Problem still persistent with Thunderbird version 2.0.0.14 (20080421) under Mac OS 10.5.4 server as fileserver and Mac OS 10.5.4 as client.
Christian, Mac crash reporting is working (at least partly I think) on trunk. Can you try again using trunk. And if that fails can you supply the info requested in comment 10?
=> incomplete without more information which we will look forward to. please reopen the bug with crash info
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Sorry for the late response. I did tests with version 2.0.0.20pre (20090104) and Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090115 Shredder/3.0b2pre. There is no crash when using an via AFP connected profile. Christian, if the crash persists and you can give us some crash information it would be really helpful. Changing to WFM meanwhile.
Resolution: INCOMPLETE → WORKSFORME
Version: unspecified → 2.0
Tried again today. Problem completely gone when using Tbird version 2.0.0.19 (20081209) and MacOS client and server 10.5.6. I guess it was an AFP issue that was fixed by Apple with the update to system 10.5.5 or 10.5.6. Thanks to you all for your efforts and your concern! All the best Christian
Resolution: WORKSFORME → FIXED
Thanks for verifying, Christian. Just a note, we only mark bugs as fixed if there is a patch attached. Restoring wfm status.
Status: RESOLVED → VERIFIED
Resolution: FIXED → WORKSFORME
Sorry and thanks, Henrik!
You need to log in before you can comment on or make changes to this bug.