Windows 10 Pro Crash #128

Closed
opened 2019-03-05 00:11:34 +00:00 by sarah · 14 comments
Owner

Received a report that 0.1.2 crashes instantly on Windows 10 Pro.

Secondary issue: we apparently have no log output available.

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.

It still crash the same way with the v0.1.3. I don't know how to send you logs of this crash.
Owner

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?

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.

Both, anyway on Windows it doesn't change if you run it from the file browser or the command line.
Owner

can you paste all the console output from running it, that would help us figure out what's going wrong, thanks!

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.

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 1/2 seconds
https://imgur.com/a/FfSus6V

Before I was just seeing a white screen.

But still, it just crashes/disappear after 1/2 seconds.

I've just installed the new version "cwtch-windows-2019-04-23-01-09.zip" Now I see this screen for 1/2 seconds https://imgur.com/a/FfSus6V Before I was just seeing a white screen. But still, it just crashes/disappear after 1/2 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"

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:
https://www.microsoft.com/it-it/p/windbg-preview/9pgjgd53tn86?rtc=1#activetab=pivot:overviewtab

The last line of the debug is this:

(6420.33d0): Break instruction exception - code 80000003 (first chance)
ntdll!LdrpDoDebuggerBreak+0x30:
00007ff9`28e311dc cc int 3

By using "WinDbg Preview" instead: https://www.microsoft.com/it-it/p/windbg-preview/9pgjgd53tn86?rtc=1#activetab=pivot:overviewtab The last line of the debug is this: (6420.33d0): Break instruction exception - code 80000003 (first chance) ntdll!LdrpDoDebuggerBreak+0x30: 00007ff9`28e311dc cc int 3

Cwtch Alpha Release 0.1.5

It is still crashing.

Cwtch Alpha Release 0.1.5 It is still crashing.
Author
Owner

Linking #190. Though will note that is a Windows 7 crash.

Linking #190. Though will note that is a Windows 7 crash.
Author
Owner

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.

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.
Owner

Actually I suspect it's because people are not running tor and the tor autorun code on windows didn't work

#199 will hopefully fix that so once it's merged I'll post a link here to the build files for testing :)

Actually I suspect it's because people are not running tor and the tor autorun code on windows didn't work #199 will hopefully fix that so once it's merged I'll post a link here to the build files for testing :)
Owner
please give these binaries a try https://build.openprivacy.ca/files/2019.08.10-02.40-cwtch-alpha-0.1.5-22-gf029da4/
Owner

closing as we did some windows quality of life improvements in August that should have resolved this

closing as we did some windows quality of life improvements in August that should have resolved this
dan closed this issue 2019-12-18 22:43:40 +00:00
This repo is archived. You cannot comment on issues.
No Milestone
No Assignees
3 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cwtch.im/ui#128
No description provided.