Opened 9 years ago

Closed 23 months ago

#4009 closed defect (wontfix)

Vidalia getting application error on exit in Win7

Reported by: erinn Owned by: chiiph
Priority: Medium Milestone:
Component: Archived/Vidalia Version:
Severity: Normal Keywords: archived-closed-2018-07-04
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Vidalia 0.2.14 / TBB 2.2.32-4 / Win7 64-bit. We had a user in #tor today who reported that sometimes (not every time) he exits TBB, he gets this error:

vidalia: vidalia.exe - Application Error
The instruction at 0x00000000 referenced memory at 0x00000000. The memory could not be written.
Click on OK to terminate the program

Some other people have reported this on the blog, arma says, so I believe it is a real issue, though I have thus far been unable to reproduce it.

Some more information gleaned from his process monitor:

15:26:07.3750548Ividalia.exeI704ICreateFileIC:\Windows\SysWOW64\WerFault.exeISUCCESSIDesired Access: Read Attributes, Disposition: Open, Options: Open Reparse 
                  Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
15:26:15.4618375Ividalia.exeI704IProcess ExitIISUCCESSIExit Status: -1073741819, User Time: 7.0200450 seconds, Kernel Time: 0.7800050 seconds, Private Bytes: 12 
                  046 336, Peak Private Bytes: 19 849 216, Working Set: 22 937 600, Peak Working Set: 30 875 648

Noting the exit status, he pointed me at this page:

Some other points worth mentioning: the user also mentioned that looking around for the original error message implied there might be some issues with DEP. After looking through my makefiles I note that I build everything in TBB with DEP/ASLR except Vidalia (which I'm fixing), so this seems possible.

Child Tickets

Change History (5)

comment:1 Changed 9 years ago by cypherpunks

I successfully compiled the latest Vidalia source for tbb with ASLR enabled, it appears to work without trouble.

However, I do also occasionally get a crash of vidalia on exit of tbb, so it is not related to ASLR (at least not in my case).

comment:2 Changed 7 years ago by sysrqb

Status: newneeds_information

Do we know if this crash is a result of a certain sequence of events? Closing Vidalia while Firefox is still running? or vice versa? We don't really have much to go on, but I'll see if I can repro.

If not and no one updates within the week, then I'll close until we receive more info.

comment:3 Changed 7 years ago by mo

We received another user report (ticket 6557 in RT) about this today.

Problem signature:
Problem Event Name: APPCRASH
Application Name: vidalia.exe
Application Version:
Application Timestamp: 50ba3144
Fault Module Name: QtCore4.dll
Fault Module Version:
Fault Module Timestamp: 4f6c7688
Exception Code: c0000005
Exception Offset: 0011b5b6
OS Version: 6.1.7601.
Locale ID: 3079
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

"This Problem occurs always with the 32 bit version of windows 7 professional.
latest service packs.
version number windows:
Microsoft Windows [Version 6.1.7601]

The problem occurs on 2 different windows installations
and is reproducible. Your software version is the latest

  1. open tor client
  2. open website, type it into the browser
  3. close browser with the x (browser closing top right) after the website has been loaded.
  4. close tor, then it crashes, and a access violation is produced.


comment:4 Changed 2 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:5 Changed 23 months ago by teor

Keywords: archived-closed-2018-07-04 added
Resolution: wontfix
Status: needs_informationclosed

Close all tickets in archived components

Note: See TracTickets for help on using tickets.