Opened 3 years ago

Closed 3 years ago

#11026 closed Bug report (wontfix)

Memory Could Not be Read

Reported by: Rick Klink Owned by:
Priority: high Component: FileZilla Client
Keywords: Referenced Memory Not Found, Error Cc:
Component version: FileZilla Client Version: 3.22.1 Operating system type: Windows
Operating system version: Windows 7

Description

I am getting the attached message every time that I logon to my webpage. It still gains access to the folders, but every time I click on one, the same message appears.

Attachments (1)

ScreenHunter_552 Oct. 09 07.06.jpg (34.0 KB) - added by Rick Klink 3 years ago.
Error Message

Download all attachments as: .zip

Change History (10)

Changed 3 years ago by Rick Klink

Error Message

comment:1 Changed 3 years ago by Tim Kosse

Status: newmoreinfo

Please go to the %LOCALAPPDATA%/CrashDumps directory, are there any crash dumps from filezilla or fzsftp? If so, please submit the most recent one.

comment:2 Changed 3 years ago by Rick Klink

Status: moreinfonew

I did as you said, but there were only Skype logs and something else, but nothing to do with Filezila or fzsftp. Thanks, Rick

comment:3 Changed 3 years ago by Tim Kosse

Status: newmoreinfo

Did you install FileZilla regularly, or are you using the the zip archive package or perhaps even a third-party distribution?

comment:4 Changed 3 years ago by Rick Klink

Status: moreinfonew

No, a long time ago and I think it was from your website. Here are the version details.

FileZilla Client


Version: 3.22.1

Build information:

Compiled for: x86_64-w64-mingw32
Compiled on: x86_64-unknown-linux-gnu
Build date: 2016-10-03
Compiled with: x86_64-w64-mingw32-gcc (GCC) 4.9.1
Compiler flags: -g -O2 -Wall -std=gnu++14

Linked against:

wxWidgets: 3.0.3
GnuTLS: 3.4.15
SQLite: 3.11.1

Operating system:

Name: Windows 7 (build 7601, Service Pack 1), 64-bit edition
Version: 6.1
Platform: 64-bit system
CPU features: sse sse2 sse3 ssse3 sse4.1 sse4.2 avx aes pclmulqdq
Settings dir: C:\Users\Sarah\AppData\Roaming\FileZilla\

comment:5 Changed 3 years ago by Rick Klink

Now I can't even send a message is it's considered spam. What's going on???

comment:6 Changed 3 years ago by Tim Kosse

The Bayes classifier really didn't like your message for some reason. I've re-trained your message as ham. Your message was:

Hello again, It's basically the program is now not useable as the messages pop-up so frequently that I cannot get any work done. Please can you help ASAP. Many thanks. Rick

comment:7 Changed 3 years ago by Tim Kosse

Status: newmoreinfo

If you open Windows' Event Viewer and go to Windows Logs -> Application after a crash, what does it show there?

comment:8 Changed 3 years ago by Rick Klink

Status: moreinfonew

Log Name: System
Source: Application Popup
Date: 11/10/2016 16:02:00
Event ID: 26
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Sarah-PC
Description:
Application popup: Windows - Application Error : The instruction at 0x772db145 referenced memory at 0xffffffff. The memory could not be read.

Click on OK to terminate the program
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Popup" />
<EventID Qualifiers="16384">26</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-10-11T15:02:00.000000000Z" />
<EventRecordID>350711</EventRecordID>
<Channel>System</Channel>
<Computer>Sarah-PC</Computer>
<Security />

</System>
<EventData>

<Data>Windows - Application Error</Data>
<Data>The instruction at 0x772db145 referenced memory at 0xffffffff. The memory could not be read.

Click on OK to terminate the program</Data>

</EventData>

</Event>

comment:9 Changed 3 years ago by Tim Kosse

Resolution: wontfix
Status: newclosed

Looks like a damaged operating system. Crashing programs normally print things like the executable name of the crashed program.

I recommend reinstalling your operating system.

Note: See TracTickets for help on using tickets.