Forum / NoMachine for Windows / Client crashes for large window
- This topic has 15 replies, 4 voices, and was last updated 5 years, 4 months ago by kosak.
-
AuthorPosts
-
April 9, 2019 at 07:52 #21961kosakParticipant
I have a setup with two 4K monitors and I typically drag my NoMachine window across both monitors.
After a recent update my client crashes if I resize the client window to be very large. I can resize it to approximately 5452 x 2091 and then the client suddenly crashes.
When I look at c:\ProgramData\NoMachine\var\log\nxtrace.log I see various crashes, not all in exactly the same place (see attached file)
I’m running Windows client 6.6.8 on Windows 10.
April 9, 2019 at 09:19 #21969TorParticipantHi kosak. Could you try again to attach the nxtrace.log file, or send it to forum[at]nomachine[dot]com please?
April 9, 2019 at 15:32 #21983graphixillusionParticipantSince the last update I got several crashes very often too. Here’s the log file.
Attachments:
April 9, 2019 at 16:23 #21986BritgirlKeymaster@graphixillusion, can you send us the client-side logs? Send them to forum[at]nomachine[dot]com and reference the topic as well. Instructions for getting logs are here: https://www.nomachine.com/DT10O00163#2
April 10, 2019 at 07:46 #21990graphixillusionParticipantThank you for the support. Log sent by email.
April 12, 2019 at 09:48 #22017BritgirlKeymasterHi, thanks for the logs. Unfortunately they didn’t reveal anything strange and we have not been able to reproduce the problem either. If you agree, we’d like to send you a debug library with further instructions on how to extract new logs. Is this ok?
April 12, 2019 at 14:13 #22023graphixillusionParticipantFor me it’s ok.
By the way when this occurs, the error in nxtrace.log is always the same:
Module: C:\Program Files (x86)\NoMachine\bin\nxplayer.bin pid 11416
Thread: 13208 exception 0xc0000005, ‘Access violation’
In: C:\Program Files (x86)\NoMachine\bin\libyuv.dll at 0x6a3981aa
Error: Invalid write to address 0x19095000
#0 0x6a3981aa libyuv.dll(SplitUVRow_Unaligned_SSE2)
#1 0x6a3aef95 libyuv.dll(SplitUVRow_Any_SSE2)
#2 0x6a3a6bef libyuv.dll(StreamConvertNV12ToI420Rect)
#3 0x65fdc8b9 libnxcim.dll(StreamConvertNV12ToI420)
April 15, 2019 at 09:03 #22030kosakParticipantHi, thanks so much for the reply…
I have sent the nxtrace.log and zip of the .nx folder to that email address you provided.
Also, because a picture is worth a thousand words, I made a YouTube video of the crash happening (twice).
In case the forum filters that link, it’s youtu.be[slash]4EgTAVWD7W4
I’m connecting to a remote machine and there’s some moderate latency, so maybe that’s a factor in why you’re not able to repro.
I’ve made it crash a few times in a row now, and my session logs all end pretty much the same way. This memory allocation thing seems to be an important clue:
ATTEMPT #1:
[…]
7768 6984 10:52:35 441.046 MonitorInfo: WARNING! Adding custom resolution 4611×1950 to monitor ID#0.
Info: Remote desktop resized to 5843×1950.
Info: Send a resize event to geometry 5984×1950 for monitor 0.
Info: Send a resize event to geometry 5843×1950 for monitor 0.
Info: Send a resize event to geometry 6176×1950 for monitor 0.
Info: Send a resize event to geometry 6257×1950 for monitor 0.
Info: Send a resize event to geometry 6411×1950 for monitor 0.
Warning: Not using hardware decoder with resolution 5856×1952.
Warning: Consider enabling hardware decoding for high resolutions in player.cfg.
7768 6984 10:52:36 475.274 MonitorInfo: WARNING! Adding custom resolution 5843×1950 to monitor ID#0.
Info: Remote desktop resized to 6257×1950.
nxplayerStartDrawing: ERROR! Frame data allocation upon resize failed with error 12: Not enough space.
Info: Remote desktop resized to 6411×1950.
ATTEMPT #2:
[…]
Info: Accepted new slave connection.
Info: Closed connection to slave server.
Warning: Not using hardware decoder with resolution 6416×2048.
Warning: Consider enabling hardware decoding for high resolutions in player.cfg.
12152 16032 11:05:41 294.561 MonitorInfo: WARNING! Adding custom resolution 6411×2041 to monitor ID#0.
[h264 @ 063eec00] concealing 8 DC, 8 AC, 8 MV errors
12152 13376 11:05:41 716.334 NXInitRgbFrame: ERROR! Can’t allocate 52690976 bytes.
ATTEMPT #3:
[…]
Warning: Not using hardware decoder with resolution 7040×1952.
Warning: Consider enabling hardware decoding for high resolutions in player.cfg.
11156 11208 11:06:29 713.222 MonitorInfo: WARNING! Adding custom resolution 7027×1950 to monitor ID#0.
11156 16272 11:06:30 978.197 ProxyReader/Reader: WARNING! Buffer for FD#1748 reached 3967020 bytes.
Info: Send a resize event to geometry 7324×1950 for monitor 0.
11156 16272 11:06:31 470.914 ProxyReader/Reader: WARNING! Buffer for FD#1748 reached 4400475 bytes.
11156 16272 11:06:31 517.778 ProxyReader/Reader: WARNING! Buffer for FD#1748 reached 4558980 bytes.
Info: Send a resize event to geometry 7567×1950 for monitor 0.
Info: Send a resize event to geometry 7572×1950 for monitor 0.
nxplayerStartDrawing: ERROR! Frame data allocation upon resize failed with error 12: Not enough space.
April 18, 2019 at 08:24 #22073BritgirlKeymasterThanks kosak and graphixillusion. We’ve found the problem affecting specifically set-ups with large screens, so are in the process of patching. We’ll then send a new patched version (full binary) for testing 🙂
April 19, 2019 at 08:07 #22084kosakParticipantFantastic news! Thanks so much to the team for working on this!
April 23, 2019 at 08:24 #22093graphixillusionParticipantI’m always glad to help! 😉
April 29, 2019 at 08:03 #22149BritgirlKeymasterKosak and Graphixillusion, you should have received an email from us with a download link 😉
May 13, 2019 at 07:35 #22292kosakParticipantSorry for the delay in responding. I dropped the ball. Anyway, unfortunately it looks like the problem is still there.
I uninstalled NoMachine from my Win10 box and installed your download. I then created a new VM in the cloud running Ubuntu 19.04 and installed NoMachine there. I can log into this machine and see a GNOME desktop but when I stretch the display too large, it crashes again.
These are the last few lines of my session file, followed by nxtrace.log
session file:
[…]
h264 @ 0646bc60] concealing 1 DC, 1 AC, 1 MV errors
[h264 @ 0646bc60] concealing 3 DC, 3 AC, 3 MV errors
[h264 @ 0646bc60] concealing 1 DC, 1 AC, 1 MV errors
[h264 @ 0646bc60] concealing 1 DC, 1 AC, 1 MV errors
[h264 @ 0646bc60] concealing 3 DC, 3 AC, 3 MV errors
Info: Send a resize event to geometry 5455×1991 for monitor 0.
Info: Remote desktop resized to 5455×1991.
Info: Send a resize event to geometry 5895×1991 for monitor 0.
Info: Remote desktop resized to 5895×1991.
Info: Send a resize event to geometry 6627×1991 for monitor 0.
Info: Remote desktop resized to 6627×1991.
Info: Send a resize event to geometry 6919×1991 for monitor 0.
nxplayerStartDrawing: ERROR! Frame data allocation upon resize failed with error 12: Not enough space.
nxtrace.log file:
Sun May 12 16:26:46 2019
————————
Module: C:\Program Files (x86)\NoMachine\bin\nxplayer.bin pid 12144
Thread: 14692 exception 0xc0000005, ‘Access violation’
In: C:\Program Files (x86)\NoMachine\bin\libqt.dll at 0x67dbed20
Error: Invalid read from address 0x10
#0 0x67dbed20 libqt.dll(ZN18QRasterPaintEngine5setDCEP5HDC__)
#1 0x67db330b libqt.dll(ZN12QNativeImageC1EiiN6QImage6FormatEbP7QWidget)
#2 0x77bd37e3 ntdll.dll(RtlFreeHeap)
#3 0x67f1f9fc libqt.dll(ZN20QRasterWindowSurface13prepareBufferEN6QImage6FormatEP7QWidget)
#4 0x74ea70b5 msvcrt.dll(free)
#5 0x74ea70d4 msvcrt.dll(free)
#6 0x67db3179 libqt.dll(ZN12QNativeImage12systemFormatEv)
#7 0x74ea70d4 msvcrt.dll(free)
May 17, 2019 at 15:36 #22360BritgirlKeymasterJust to let you know that our developers are still working on this.
June 12, 2019 at 09:35 #22643BritgirlKeymaster@kosak @graphixillusion, please check your inbox. We have sent you a link to the patched package for testing.
-
AuthorPosts
This topic was marked as solved, you can't post.