FS#36847 - [filezilla] crashes on download

Attached to Project: Community Packages
Opened by Joyce Markoll (Melodie) - Tuesday, 10 September 2013, 00:22 GMT
Last edited by Florian Pritz (bluewind) - Thursday, 31 October 2013, 10:57 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Florian Pritz (bluewind)
Jelle van der Waa (jelly)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Filezilla keeps crashing in a 64bits Archlinux install.


Additional info:
* package version(s)
filezilla-3.7.3-1-x86_64

* config and/or log files etc.
Config:
*******
$ lscpu
Architecture : x86_64
Mode(s) opératoire(s) des processeurs : 32-bit, 64-bit
Boutisme : Little Endian
Processeur(s) : 2
Liste de processeur(s) en ligne : 0,1
Thread(s) par cœur : 1
Cœur(s) par socket : 2
Socket(s) : 1
Nœud(s) NUMA : 1
Identifiant constructeur : AuthenticAMD
Famille de processeur : 16
Modèle : 6
Nom de modèle : AMD Athlon(tm) II X2 260 Processor
Révision : 3
Vitesse du processeur en MHz : 800.000
BogoMIPS : 6432.55
Virtualisation : AMD-V
Cache L1d : 64K
Cache L1i : 64K
Cache L2 : 1024K
Nœud NUMA 0 de processeur(s) : 0,1
$
*******

$ uname -r ; pacman -Q linux
3.10.10-1-ARCH
linux 3.10.10-1
$

*******

Starting it from gdb strangely makes it work until the job is done:

*******
$ gdb filezilla
GNU gdb (GDB) 7.6.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/filezilla...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/filezilla
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe7fce700 (LWP 1124)]
[New Thread 0x7fffe75c5700 (LWP 1125)]

*******

Starting it from the console brings more messages and information about the crash.

I tried yesterday, and I tried again today after removing completely the package (pacman -Rnsc filezilla) and reinstalling it from the PKGBUILD, the result is the same. I attach the the output of the console as text file here after.

Steps to reproduce:
Get Filezilla to run in a 64bits arch install and download a complete tree directory (a website is what I wanted to download with Filezilla, for backup purpose.

Of course if this issue comes from something wrong in my machine I'd be interested to have a clue about it (all other programs work perfect so far).

If you need other logs from just after the crash, please let me know and I will bring more.

Regards,
Mélodie
This task depends upon

Closed by  Florian Pritz (bluewind)
Thursday, 31 October 2013, 10:57 GMT
Reason for closing:  Works for me
Comment by Joyce Markoll (Melodie) - Tuesday, 10 September 2013, 02:03 GMT
Hi,

I installed the x86_64 version from the Filezilla sourceforge repo and I have been able to do tasks during quite some time. I tried to start it from console, downloaded a whole website; then I close it and started it from the menus, and have done several kinds of tasks during quite some time, on one website, on two at a time each in it's own tab.

The program did not crash at all.

This is what I have installed:
FileZilla_3.7.3_x86_64-linux-gnu.tar.bz2 (5.5 MB) - http://sourceforge.net/projects/filezilla/files/latest/download?source=files

(under the /usr/local directory (each file at it's right place in the tree directory).

Here is the direct link of the tarball: http://downloads.sourceforge.net/project/filezilla/FileZilla_Client/3.7.3/FileZilla_3.7.3_x86_64-linux-gnu.tar.bz2

The thing is it is already all compiled…

Comment by Florian Pritz (bluewind) - Tuesday, 10 September 2013, 09:39 GMT
Can't reproduce this here, but I only tested browsing a bit and downloading a small directory tree.
Comment by Joyce Markoll (Melodie) - Thursday, 12 September 2013, 12:56 GMT
Hi Florian,
Does your machine have the same configuration? The proc from my machine has the following flags:
****
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate npt lbrv svm_lock nrip_save

****



* I had also tried to recompile it in my machine and I had not more luck with that;

* Strangely I don't see the attachment I put when I opened this bug report;

* How come the severity is presented as "Low" ? I can't use the repos version at all. (?)

Trying to attach the file from the console message again… if it does not upload, you can find the whole content also here:
http://pastebin.fr/28712

Regards,
Mélodie



Comment by Florian Pritz (bluewind) - Monday, 28 October 2013, 15:00 GMT
I still can't reproduce this and cpu flags don't matter. If recompiling doesn't fix it for you, but the upstream binary works this could be caused by compiler options, linker options or something else. Nothing I can find/fix.

Please try compiling a debug package or talk to upstream.

Loading...