there is a user in #tor that is reporting tor messenger crashing on windows 10
"seems it crashes inside directx dlls trying to write to a null pointer"
Workaround:
ticket:17453#comment:7
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
I can confirm that it crashes on Win7 64-bit pro with EMET installed and using the default settings. No specific rules have been added for Instantbird, and EMET has DEP and ASLR set to always-on, and SEHOP set to application opt-out.
I am running a physical machine, but other users may be running Windows VMs.
This has been an issue for alphas #1-3 and the latest beta. I tried disabling EMET for the alphas, no luck there. I haven't tried disabling EMET for the latest beta, though.
It seems like a number of users are having this issue on many versions of Win7, 8, 8.1, 10. Most users appear to be running 64-bit Windows but at least one is running Windows 8.1 32-bit.
One user did report it working on a Windows Server 2012 R2 VM.
"On October 29th, 2015 Anonymous said:
I had posted earlier about tor messenger not working on Win 8.1. Although it works on my Win server 2012 R2 VM."
Some bug reports are showing up on the blog, and I have posted the technical details here. There are many more reports that don't have those details, and possibly more reports in forums/IRC (which I don't monitor).
From the blog (not me):
"On October 29th, 2015 Anonymous said:
Problem signature:
Problem Event Name: APPCRASH
Application Name: instantbird.exe
Application Version: 41.0.0.5729
Application Timestamp: 000232e8
Fault Module Name: d2d1.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7b7aa
Exception Code: c0000005
Exception Offset: 0001f3ba
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789"
Another user, also not me:
"On October 29th, 2015 Anonymous said:
It doesn't work at all, Windows 7 64bit, Windows 8.1 32bit, and Windows 10 64bit.
"On October 29th, 2015 Anonymous said:
Crash
Сигнатура проблемы:
Имя события проблемы: APPCRASH
Имя приложения: instantbird.exe
Версия приложения: 41.0.0.5729
Отметка времени приложения: 000232e8
Имя модуля с ошибкой: d2d1.dll
Версия модуля с ошибкой: 6.1.7601.17514
Отметка времени модуля с ошибкой: 4ce7b7aa
Код исключения: c0000005
Смещение исключения: 0001f3ba
Версия ОС: 6.1.7601.2.1.0.256.1
Код языка: 1049
Дополнительные сведения 1: 0a9e
Дополнительные сведения 2: 0a9e372d3b4ad19135b953a78882e789
Дополнительные сведения 3: 0a9e
Дополнительные сведения 4: 0a9e372d3b4ad19135b953a78882e789"
And also:
"On October 29th, 2015 Anonymous said:
It doesn't open on my machine. It gives an error: 0x0000000070C19BD5 made reference to the memory on 0x0000000000000000. The memory can't be written.
If i launch it as admin it just loads but nothing happens, won't open and won't display any error.
Does this require something else in order to work?"
(This user mentioned running Windows 10 in a later comment)
Seems like this is your version of #9145 (moved). See that ticket for workarounds. (I guess you don't set gfx.direct2d.disabled and layers.acceleration.disabled to true, right?)
Thank you! Verified working on Win7 64-bit. Changes made to prefs.js in the tor-launcher folder, as well as the prefs.js in the default profile folder and the prefs.js in the profile folder created on first run.
(I really should have recognized this bug when I got safe mode working...three months ago. Argh!)
So the workaround for users who don't want to wait for the next release is to create the file Messenger/TorMessenger/Data/Browser/profile.default/prefs.js with the following two lines:
After this was reported, I checked on a Windows 10 machine where it was crashing. boklm's recommendation fixes this problem. We should update the blog post or make a new release.
Er thanks. Sorry, just confirming what can be the issue here since I have verified independently on two machines that this should solve the issue. We will comment here if there is an update.
I think I made a mistake in the file path. It should be Messenger/TorMessenger/Data/Browser/profile.default/prefs.js (not in the preferences directory). I've edited the previous comment to fix it.
I think I made a mistake in the file path. It should be Messenger/TorMessenger/Data/Browser/profile.default/prefs.js (not in the preference directory).
OK that can be it. I didn't follow your path because I knew where the file should go. Let's hope this nails it down.
I think I made a mistake in the file path. It should be Messenger/TorMessenger/Data/Browser/profile.default/prefs.js (not in the preference directory).
OK that can be it. I didn't follow your path because I knew where the file should go. Let's hope this nails it down.
Trac: Description: > there is a user in #tor that is reporting tor messenger crashing on windows 10
"seems it crashes inside directx dlls trying to write to a null pointer"
to
there is a user in #tor that is reporting tor messenger crashing on windows 10
"seems it crashes inside directx dlls trying to write to a null pointer"