Opened 14 years ago

Last modified 13 years ago

#828 closed Bug report

Failure when trying to upload file

Reported by: stove Owned by: Alexander Schuch
Priority: normal Component: FileZilla Client
Keywords: Cc: stove, Alexander Schuch
Component version: Operating system type:
Operating system version:

Description

Filezilla crashes when attempting to resume on server
that has weird directory permissions, if i upload
entire contents of directory, it eventually hangs after
about 30 seconds.

Bandwidth throttling is on, and server has wstrange
permissions.

NOt sure what other information I can obtain.

Exception report created by FileZilla version 2.2.12
===================================================

System details:


Operating System: Microsoft Windows XP
Professional Service Pack 2 (Build 2600)
Processor Information: Vendor: GenuineIntel, Speed:
2399MHz, Type: Intel Pentium compatible, Number Of
Processors: 1, Architecture: Intel, Level: Unknown 15,
Stepping: 5-19
Memory Information: Memory Used 49%, Total Physical
Memory 785904KB, Physical Memory Available 397976KB,
Total Virtual Memory 2097024KB, Available Virtual
Memory 2051428KB, Working Set Min: 200KB Max: 1380KB .

Exception Details:


Exception code: C0000005 ACCESS_VIOLATION

Change History (4)

comment:1 Changed 14 years ago by stove

It works when i manually pick which files to upload, not
sure what causes hang. It's uploading fine now, after i
deselected which files were already on remote end.

comment:2 Changed 13 years ago by Alexander Schuch

Can you please re-try with current FileZilla 2 (or even with
FileZilla 3 latest beta) and check if the problem still
persists?

If FileZilla hangs but doesn't crash, can you please attach
the complete message log to this item? If it crashes, a
backtrace is needed to analyse the problem.

Based on the information given, the bug cannot be fixed as
there is not enough information about how to trigger it.

comment:3 Changed 13 years ago by sf-robot

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

comment:4 Changed 13 years ago by stove

I wasn't able to reproduce it more since the latest version. Not sure if it was ever fixed, or just a random crash. Leave it closed. :)

Note: See TracTickets for help on using tickets.