Enpass crashing on ultrawide resolution

[Kurt]

Hello community,

after upgrading my monitor to an super ultra wide on (5120x1440p) Enpass keeps crashing and freezing on startup.

If I turn down the resolution to 1080p, then there is no problem and everything works fine.

Also running it from the terminal only prints out this Error: "QQmlComponent: Created graphical object was not placed in the graphics scene."

Any help is appreciated.

OS: Linux Manjaro
Enpass Version: 6.0.6.323

Edited April 15, 2019 by Kurt

[Guest Vikram Dabas]

Hi,

Sorry for the late reply.

The highest resolution that we've tested on which the app is working fine is up to 3840x2160 (21:9). Please check this FAQ and set the scale factor accordingly.

If you still face any problem then share the Crash report via DM.

[Kurt]

Thank you for your reply. Changing the scale factor didn't help, but I don't know where to find the Crash report. Could you please explain me where to find it?

[Dentonthebear]

17 hours ago, Kurt said:

Thank you for your reply. Changing the scale factor didn't help, but I don't know where to find the Crash report. Could you please explain me where to find it?

Hi Kurt,

I think it should be in the /var/crash folder.

[Guest Vikram Dabas]

Hi @Kurt

When you open the app after it got crashed, you will see a crash report dialog box. Please mention the reproducible steps along with your name in the comment box and click Send Report to share it with us.

[Belogron]

Hi, dropping in to report that I am currently facing the same issue here.

Using the same resolution (5120x1440p) Enpass chrashes on start, but freezes the PC for about 5min. I did some checking, here are my findings:

When starting Enpass, it starts to rapidly fill up the system memory. In around 20sec it fills the 32GB RAM in my machine, then everything freezes for about 3min (pink bar in screenshot). For the system, no time passes here. Afterwards, I can see that the Swap (another 32GB) are being filled up as well. Where the yellow bar is drawn, another ~1min freeze occurs. Afterwards, memory consumption drops drastically, as the OS has killed the process.

The following data can then be grabbed from dmesg:

[25921.488671] Enpass invoked oom-killer: gfp_mask=0x100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), order=0, oom_score_adj=0
[25921.488673] CPU: 15 PID: 148687 Comm: Enpass Tainted: P           OE     5.6.6-200.fc31.x86_64 #1
[25921.488674] Hardware name: System manufacturer System Product Name/ROG STRIX X470-F GAMING, BIOS 4008 04/13/2018
[25921.488674] Call Trace:
[25921.488681]  dump_stack+0x66/0x90
[25921.488684]  dump_header+0x4a/0x1e2
[25921.488685]  oom_kill_process.cold+0xb/0x10
[25921.488686]  out_of_memory+0x226/0x4c0
[25921.488688]  __alloc_pages_slowpath+0xb32/0xdd0
[25921.488690]  __alloc_pages_nodemask+0x2c9/0x310
[25921.488692]  alloc_pages_vma+0x79/0x220
[25921.488694]  __handle_mm_fault+0xacc/0x15a0
[25921.488696]  ? call_function_single_interrupt+0xa/0x20
[25921.488698]  handle_mm_fault+0xc4/0x1f0
[25921.488700]  do_user_addr_fault+0x1f9/0x450
[25921.488701]  page_fault+0x3e/0x50
[25921.488703] RIP: 0033:0x16bb8bf
[25921.488705] Code: f4 48 c1 e1 04 4c 01 c1 66 0f 70 c1 00 48 39 c1 76 35 66 0f 1f 84 00 00 00 00 00 66 0f e7 40 d0 66 0f e7 40 e0 66 0f e7 40 f0 <66> 0f e7 00 48 83 c0 40 48 39 c1 77 e4 4c 29 c1 48 8d 41 cf 48 83
[25921.488705] RSP: 002b:00007ffce6179c18 EFLAGS: 00010202
[25921.488706] RAX: 00007fa4fc97b000 RBX: 000000000614e300 RCX: 00007fa5332f4010
[25921.488707] RDX: 00000000046ed900 RSI: 0000000000000000 RDI: 00007fa4ec41b010
[25921.488707] RBP: 00007ffce6179eb0 R08: 00007fa4ec41b010 R09: 0000000000000000
[25921.488708] R10: 0000000000000022 R11: 0000000000000246 R12: 000000000614e2d0
[25921.488708] R13: 0000000000000006 R14: 00007ffce6179eb0 R15: 00000000060c7d90
[25921.488710] Mem-Info:
[25921.488712] active_anon:7376797 inactive_anon:11216 isolated_anon:29
                active_file:238 inactive_file:99 isolated_file:0
                unevictable:8 dirty:0 writeback:1187238 unstable:0
                slab_reclaimable:40508 slab_unreclaimable:541340
                mapped:44787 shmem:314 pagetables:37242 bounce:0
                free:48059 free_pcp:0 free_cma:0
[25921.488714] Node 0 active_anon:29507188kB inactive_anon:44864kB active_file:952kB inactive_file:396kB unevictable:32kB isolated(anon):116kB isolated(file):0kB mapped:179148kB dirty:0kB writeback:4748952kB shmem:1256kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no
[25921.488715] Node 0 DMA free:15880kB min:32kB low:44kB high:56kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15996kB managed:15900kB mlocked:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[25921.488716] lowmem_reserve[]: 0 3417 31984 31984 31984
[25921.488718] Node 0 DMA32 free:116228kB min:7216kB low:10712kB high:14208kB reserved_highatomic:0KB active_anon:3449624kB inactive_anon:124kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:18984kB present:3596832kB managed:3596336kB mlocked:0kB kernel_stack:0kB pagetables:13012kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[25921.488720] lowmem_reserve[]: 0 0 28567 28567 28567
[25921.488721] Node 0 Normal free:60128kB min:60332kB low:89584kB high:118836kB reserved_highatomic:2048KB active_anon:26057512kB inactive_anon:44300kB active_file:824kB inactive_file:236kB unevictable:32kB writepending:4730280kB present:29871616kB managed:29261104kB mlocked:32kB kernel_stack:17088kB pagetables:135956kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
[25921.488722] lowmem_reserve[]: 0 0 0 0 0
[25921.488723] Node 0 DMA: 0*4kB 1*8kB (U) 0*16kB 0*32kB 2*64kB (U) 1*128kB (U) 1*256kB (U) 0*512kB 1*1024kB (U) 1*2048kB (M) 3*4096kB (M) = 15880kB
[25921.488727] Node 0 DMA32: 581*4kB (UM) 188*8kB (UME) 265*16kB (UM) 202*32kB (UM) 225*64kB (UE) 152*128kB (UME) 93*256kB (UM) 44*512kB (UM) 13*1024kB (UE) 2*2048kB (UM) 1*4096kB (M) = 116228kB
[25921.488730] Node 0 Normal: 217*4kB (UME) 7125*8kB (UMH) 91*16kB (UMH) 10*32kB (UMH) 3*64kB (H) 1*128kB (H) 1*256kB (H) 0*512kB 1*1024kB (H) 0*2048kB 0*4096kB = 61244kB
[25921.488734] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
[25921.488735] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
[25921.488735] 1194236 total pagecache pages
[25921.488738] 1193671 pages in swap cache
[25921.488739] Swap cache stats: add 35738056, delete 34604040, find 1787170/2446868
[25921.488739] Free swap  = 0kB
[25921.488739] Total swap = 33554428kB
[25921.488740] 8371111 pages RAM
[25921.488740] 0 pages HighMem/MovableOnly
[25921.488740] 152776 pages reserved
[25921.488740] 0 pages cma reserved
[25921.488740] 0 pages hwpoisoned
[25921.488740] Tasks state (memory values in pages):
[25921.488741] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name
[25921.488747] [   1300]     0  1300    19814        0   172032      441          -250 systemd-journal
[25921.488749] [   1315]     0  1315     9480        1   102400     1506         -1000 systemd-udevd
[25921.488750] [   1603]     0  1603     6246        0    61440      185         -1000 auditd
[25921.488752] [   1625]    81  1625    67228        0    53248      239          -900 dbus-broker-lau
[25921.488753] [   1626]    81  1626     2611        0    57344     1433          -900 dbus-broker
[OTHER PROCESSES REMOVED FOR PRIVACY]
[25921.488893] [ 148687]  1000 148687 14251774  6090554 110587904  7659507             0 Enpass
[OTHER PROCESSES REMOVED FOR PRIVACY]
[25921.488899] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service,task=Enpass,pid=148687,uid=1000
[25921.488922] Out of memory: Killed process 148687 (Enpass) total-vm:57007096kB, anon-rss:24362208kB, file-rss:0kB, shmem-rss:8kB, UID:1000 pgtables:107996kB oom_score_adj:0
[25923.153275] oom_reaper: reaped process 148687 (Enpass), now anon-rss:0kB, file-rss:0kB, shmem-rss:8kB

Switching to a smaller resolution allows me to start Enpass again, however no option to send a crash report shows up.

Once Enpass is launched, I can switch resolution back to ultrawide and Enpass keeps working and is scaled perfectly.

So apparently just a problem on startup.

Edit:

When launching from the terminal, the String

Quote

QQmlComponent: Created graphical object was not placed in the graphics scene.

gets logged exactly 185 times.

Still no dialogue to send an error report after a successful launch, even after enabling Logs. Logs reports "Nothing to show here"

Edited May 13, 2020 by Belogron
Added more information

[Pratyush Sharma]

Hi @Belogron,

Sorry for the inconvenience caused to you.

Please let us know the following details so we can help you better.

• On which device (along with OS version) are you using Enpass?
• Which Enpass version are you using?
• Which cloud are you using to sync?
• Also, let us know how many items you have in Enpass App?

Thanks!

[Belogron]

Hi @Pratyush Sharma, thanks for getting back at me.

Quote

On which device (along with OS version) are you using Enpass?

It is a desktop PC using a Ryzen 7 2700X and GTX 1080. I am running Fedora 31, Kernel version 5.6.11-200.fc31.x86_64. I am using X11 and GNOME 3.34.6

Quote

Which Enpass version are you using?

I am running the latest version for your official RPM repo, 6.4.1.643-1

Quote

Which cloud are you using to sync?

Google Drive

Quote

Also, let us know how many items you have in Enpass App?

There are currently 318 entries in Enpass.

 

By the way, Enpass Windows version on exactly the same hardware on up-to-date Win 10 works flawlessly.

If you need further infos, I'll try to get back to you asap.

 

Thanks a lot!

[Pratyush Sharma]

Hi @Belogron,

Thanks for sharing the details.

I have noted down this issue and notified the QA team to look into it.

Thanks for your co-operation.

[Garima Singh]

Hey @Belogron,

Thanks for the patience.

We would like to share that the issue has been reproduced and assigned to the Dev team to resolve and hopefully, a fix will be available in the future update.

Thanks for your co-operation.

[Rudy]

I'm seeing the same behaviour

 

  Installed: 6.4.1.643
  Candidate: 6.4.1.643
  Version table:
 *** 6.4.1.643 500
        500 https://apt.enpass.io stable/main amd64 Packages
        100 /var/lib/dpkg/status
 

[Pratyush Sharma]

Hi @Rudy,

Welcome to the forums!

We are already aware of this issue and our Dev team is working on it. Hopefully, fix will be available in the future update. Till then, we will request you to please co-operate with us.

Thanks!

[random_Enpass_user]

I suffered from the same out of memory crash on my 5120x1440 display on Linux and adding the following to my environment helped:

export QT_AUTO_SCREEN_SCALE_FACTOR=0
export QT_SCREEN_SCALE_FACTORS=1

I've added those to my ~/.bashrc but YMMV depending on your shell etc.
 

[Garima Singh]

Hey @random_Enpass_user

Welcome to the forum and thanks for sharing your inputs. Will notify this to the concerned team.

Thanks.