Desktop Synchronization Client crashes on Mac High Sierra on start #6191
Labels
macOS
p2-high
Escalation, on top of current planning, release blocker
ReadyToTest
QA, please validate the fix/enhancement
type:bug
Milestone
Comments
|
@migs540 thanks for pointing this out. Did you submit a crash report when the issue happened? Will take a look at the logs in nextcloud/desktop#57 (comment) to see if something rings a bell in there. |
|
If you are asking whether i clicked on "send" or "don't send" I clicked on send. Is that what you mean @SamuAlfageme ? other open issue referenced: with tail showing: |
|
@migs540 hm. It does look like #6049, we patched a few things up around this in #6161 Could you give 2.4.0 beta1 from https://owncloud.org/changelog/desktop/ a try to see if it solved your problem? |
|
Sorry, no good, same error with new version (it died a minute ago and I clicked "send" in the dialogue). |
|
My current workaround is to use file sharing from one mac (high sierra where owncloud own't run) to another mac (previous os version) where the desktop client runs. It's a really clunky workaround. All errors above from high sierra mac. |
|
So we don't need to fish our the crash trace from the crash handler: Then on crash type: :) |
|
@guruz damn, could this be an edge case of #5650? I can't find anything relatable to the logs in high-sierra on sentry |
|
thread apply all bt isn't recognised. I can get to "thread" but not "thread apply" - see below for usage and let me know if you want me to run another command. |
|
@migs540 Mixed up the gdb and lldb syntax :-/
could work? |
|
@guruz I tried a few things. Out of my depth: key line: error: Process must be launched. |
|
Type „run“ ...
…Sent from my iPhone
On 27. Nov 2017, at 13:52, michael grau ***@***.***> wrote:
I tried a few things. Out of my depth:
key line: error: Process must be launched.
(lldb) thread backtrace all
error: invalid thread
(lldb) thread backtrace
error: invalid thread
(lldb) thread
Commands for operating on one or more threads in the current process.
Syntax: thread
The following subcommands are supported:
backtrace -- Show thread call stacks. Defaults to the current thread, thread indexes can be specified as arguments. Use
the thread-index "all" to see all threads.
continue -- Continue execution of the current target process. One or more threads may be specified, by default all
threads continue.
info -- Show an extended summary of one or more threads. Defaults to the current thread.
jump -- Sets the program counter to a new address.
list -- Show a summary of each thread in the current target process.
plan -- Commands for managing thread plans that control execution.
return -- Prematurely return from a stack frame, short-circuiting execution of newer frames and optionally yielding a
specified value. Defaults to the exiting the current stack frame. Expects 'raw' input (see 'help raw-input'.)
select -- Change the currently selected thread.
step-in -- Source level single step, stepping into calls. Defaults to current thread unless specified.
step-inst -- Instruction level single step, stepping into calls. Defaults to current thread unless specified.
step-inst-over -- Instruction level single step, stepping over calls. Defaults to current thread unless specified.
step-out -- Finish executing the current stack frame and stop after returning. Defaults to current thread unless
specified.
step-over -- Source level single step, stepping over calls. Defaults to current thread unless specified.
step-scripted -- Step as instructed by the script class passed in the -C option.
until -- Continue until a line number or address is reached by the current or specified thread. Stops when returning
from the current function as a safety measure. The target line number(s) are given as arguments, and if more
than one is provided, stepping will stop when the first one is hit.
For more help on any particular subcommand, type 'help <command> <subcommand>'.
(lldb) thread info
error: Process must be launched.
(lldb) r
Process 22529 launched: '/Applications/owncloud.app/Contents/MacOS/owncloud' (x86_64)
2017-11-27 20:50:29.505929+0800 owncloud[22529:3996608] MessageTracer: load_domain_whitelist_search_tree:73: Search tree file's format version number (0) is not supported
2017-11-27 20:50:29.505976+0800 owncloud[22529:3996608] MessageTracer: Falling back to default whitelist
m_crashReporterChar: /Applications/owncloud.app/Contents/MacOS/owncloud_crash_reporter
m_crashReporterWChar: /Applications/owncloud.app/Contents/MacOS/owncloud_crash_reporterDump file was written to: /var/folders/y0/3dv2xzq15qq_5qvzwvb1_z3m0000gn/T/689F47E8-52C5-43A5-A3C6-466CA6BA65E1.dmp
Process 22529 exited with status = 1 (0x00000001)
(lldb) thread info
error: Process must be launched.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Same reason behind: #6074 (comment) |
|
r is short for run so it's the same behaviour see below ...So I should close this one as it's the same as #6074? |
guruz
added
type:bug
p2-high
|
@SamuAlfageme ufff... thanks. Sounds very related then @migs540 Ah, because the build is compiled with the crash reporter compiled in, you can't use lldb it seems because it will be wrapped and exited. Let me check how you could still do it (and prove it's the same as @xnicolay in #6074 (comment) |
|
In your home -> |
|
I have the same issues on my mac: |
|
@MrBetatester Thanks for the backtrace! So at least part of this is #6123 |
|
@guruz with crashreporter set to false |
|
I'm new to github... what's the right thing to do with this now it's listed as a bug? Do I close it, leave it open or amend it in some way? |
|
leave it open until the bug is fixed I think https://github.com/owncloud/client/blob/master/src/gui/generalsettings.cpp line 49 is the issue. Maybe the app name is not set because the app isn't finish with the startup. I will build my own client tomorrow and try to fix it by my self. |
|
@MrBetatester @migs540 Can you please test with https://download.owncloud.com/desktop/daily/ownCloud-2.4.0.8665-nightly20171128.pkg ? |
guruz
added
ReadyToTest
|
@guruz Great news, it works for me. Let me know if you want me to run any specific tests. Awesome stuff. |
|
@migs540 Yay :) You can test if having the client launch on startup/login still works (there is a checkbox setting in the Settings dialog for it) |
|
@guruz OK I'll startup tomorrow. Just paused it because I am getting a massive amount of _conflict files generated. |
|
@guruz yes it is working again. Autostart also works but it was not enabled as default? |
|
Great : now, i can remember what owncloud seems ! |
|
Fantastic 👏 |
|
I'm experiencing this on a fresh install of High Sierra with the latest stable, and the latest 2.4 nightlies. |
|
I tried installing from homebrew, and that worked |
|
@mazubieta That's a different one which is tracked in #6268 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Upgrade to High Sierra
Start owncloud via applications/owncloud
Upgrade (and or remove existing owncload and replace with 2.3.4 or 2.4 (beta)
Any diagonostic advice will be taken. I can't find any logs other than a dmp file.
Expected behaviour
Owncloud desktop app opens and runs and is visible in taskbar
Actual behaviour
Owncloud crashes immediately with error: "Sorry! Owncloud crashed please tell us about it!..."
Server configuration
Operating system:
mac os 10.13.1
Web server:
na
Database:
na
PHP version:
na
ownCloud version: (see ownCloud admin page)
2.3.4 or 2.4
Updated from an older ownCloud or fresh install:
either
Where did you install ownCloud from:
https://download.owncloud.com/desktop/stable/ownCloud-2.3.4.8537.pkg
The text was updated successfully, but these errors were encountered: