[bug] Windows x86 build kind of freezes when started

[charlescanato]

When starting a x86 build, Quentier starts, loads the UI but does not becomes really available for use.

It's like it's frozen, but not like a "not responding" application (and then Win handles its crash). It's more like it seems it is running but does not respond to UI events. Menus don't open, I can't move the window, tray icon opens context menu, but doesn't respond (cursor doesn't even change when over it).

But if I leave the application alone, sometimes I can see status bar presenting an error or sync message. Logs are also being generated. I'm sending you (by e-mail) the link for a share for my logs/files.

However, I must be clear. This isn't really a great problem for me, and it seems to me one of those boring issues to find - I hope it's not. I don't feel nowadays there's a huge audience for x86 apps, but I do like to use them when I'm guessing that the application won't benefit of x64 addressing/processing. However, it doesn't bother me to use x64 if x86 isn't working or available.

This has always happened, I just thought it was something I messed up the first time, and then went to x64 versions. Both setup or portable, stable or unstable versions present the same behavior.

Steps to reproduce the problem

1. Start Quentier x86
2. Click on any part of the application window

Expected behavior Any answer to a click, in any part of the application window: for example, clicking on a message on the message list should present it in the message panel.

Environment info Please provide the information about the environment in which Quentier is run:

1. Win7-64
2. Which version of Quentier do you use - happens on both stable and unstable, but this test was on last unstable
3. Where did you install Quentier from - GitHub releases

Additional context As I said, this isn't a great problem for me, since x64 version does not present this problem on my end. Anyway, I felt it could be important to report it.

[d1vanov]

Hi there, received the link to the logs from you, thanks. Do I understand correctly that this issue doesn't occur with x64 version of Quentier?

[d1vanov]

Looked through the logs, don't see anything relevant to this particular issue there. I'm not sure I can debug this without access to a Windows machine, probably most I could do is try to search something online about problems like this with x86 Qt on x64 Windows.

[charlescanato]

I don't know about you, but I would totally make this one lowest of the lowest priorities, lol. I just found it weird, but it isn't a showstopper for me in any way. You got it, it does not happen with Windows x64 version.

[d1vanov]

Couple of random things I can suggest to try:

1. Set environment variable QTWEBENGINE_DISABLE_SANDBOX to 1 and then start Quentier in such environment. I.e. in cmd terminal:

> set QTWEBENGINE_DISABLE_SANDBOX=1
> quentier.exe

2. Try to start Quentier in Windows XP compatibility mode.

[charlescanato]

Tried both things. Unfortunately, none of them offered any change.

[d1vanov]

I did some research - this might be caused by QtWebEngine - the component behind Quentier's note editor. According to what I was able to find, its 32 bit version might not work correctly on 64 bit Windows. I'm not quite sure that's the cause but honestly I don't know what else could be. Maybe I should just discontinue shipping 32 bit Windows binaries. Support for 32 bit Windows has been dropped in Qt 6 anyway and at some point Quentier would have to migrate to Qt 6.

[charlescanato]

Only way to confirm that would be for me to find a copy of Win7 (or Vista or XP) 32-bit and test it under a VM. Can't say I'm dying for doing it, lol, but I can do it, just maybe with a lower priority.

OTOH, that would be really just for testing this hypothesis. I agree with you. Anyone would be fully served with only the 64-bit version.

Thanks for having kept researching!