Windows 10 Pro Crash #128

建立問題

sarah · 2019-03-05T00:11:34Z

sarah " 評論

2019-03-05 00:11:34 +00:00

"

管理員

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.

HostFat " 評論

2019-03-26 19:33:07 +00:00

"

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.

dan " 評論

2019-03-27 19:13:25 +00:00

"

管理員

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?

HostFat " 評論

2019-03-27 19:45:44 +00:00

"

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

dan " 評論

2019-03-29 00:46:31 +00:00

"

管理員

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

HostFat " 評論

2019-03-29 00:48:08 +00:00

"

There isn't any console output on running by command line, on Windows 10 Pro.

HostFat " 評論

2019-04-23 01:46:49 +00:00

"

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.

HostFat " 評論

2019-04-23 01:59:31 +00:00

"

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"

HostFat " 評論

2019-04-23 02:29:52 +00:00

"

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

HostFat " 評論

2019-07-30 23:08:14 +00:00

"

Cwtch Alpha Release 0.1.5

It is still crashing.

Cwtch Alpha Release 0.1.5 It is still crashing.

sarah " 評論

2019-07-31 17:16:37 +00:00

"

管理員

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

sarah " 評論

2019-08-07 18:26:00 +00:00

"

管理員

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.

dan " 評論

2019-08-10 02:21:36 +00:00

"

管理員

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 :)

dan " 評論

2019-08-10 02:42:14 +00:00

"

管理員

please give these binaries a try

https://build.openprivacy.ca/files/2019.08.10-02.40-cwtch-alpha-0.1.5-22-gf029da4/

please give these binaries a try https://build.openprivacy.ca/files/2019.08.10-02.40-cwtch-alpha-0.1.5-22-gf029da4/

dan " 評論

2019-12-18 22:43:40 +00:00

"

管理員

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