Received a report that 0.1.2 crashes instantly on Windows 10 Pro.
Secondary issue: we apparently have no log output available.
It still crash the same way with the v0.1.3.
I don’t know how to send you logs of this crash.
How are you running it? Can we get a bit more information? are you just double clicking on the app from the file browser, or running it form the command line?
Both, anyway on Windows it doesn’t change if you run it from the file browser or the command line.
can you paste all the console output from running it, that would help us figure out what’s going wrong, thanks!
There isn’t any console output on running by command line, on Windows 10 Pro.
I’ve just installed the new version “cwtch-windows-2019-04-23-01-09.zip”
Now I see this screen for ½ seconds
Before I was just seeing a white screen.
But still, it just crashes/disappear after ½ seconds.
I’m not sure if this can be useful, but by debugging the exe from vs2019, the first line says this
“onecore\com\combase\objact\objact.cxx(834)\combase.dll!00007FF927CF7213: (caller: 00007FF927CF64D6) ReturnHr(1) tid(2cb0) 800401F0 CoInitialize has not been called.”
And this is the last before the crash:
“QObject::~QObject: Timers cannot be stopped from another thread”
By using “WinDbg Preview” instead:
The last line of the debug is this:
(6420.33d0): Break instruction exception - code 80000003 (first chance)
00007ff9`28e311dc cc int 3
Cwtch Alpha Release 0.1.5
It is still crashing.
Linking #190. Though will note that is a Windows 7 crash.
Copied from #190: We are now pretty convinced that this is being caused by our logging framework which does not appear to handle windows (our windows builds work if launched from a POSIX compatible environment like cygwin)
Aim is to update that framework this sprint, and get a working build on native windows.
Actually I suspect it’s because people are not running tor and the tor autorun code on windows didn’t work
please give these binaries a try
closing as we did some windows quality of life improvements in August that should have resolved this
No due date set.
This issue currently doesn't have any dependencies.
Deleting a branch is permanent. It CANNOT be undone. Continue?