Main Board > Thin Client/WindX
Windx Memory access violation?
Cedric:
Am I the only one having problems with "memory access violation" randomly on the client side (windx) while loading a screen since updated to V16. It's not necessarily the same screen loading... could be any screen. Some day, users don't experience the issues at all, but other days it could happen 5-6 times a day. Not all client has the issues, but I'd say probably 50 out of 90 clients has reported the problem.
Somebody understands the log attached? (from windx)
Mike King:
There was an issue on early versions of v16 caused by using ESC as a field separator in a list box. With the ability to add pictures, bar graphs colors and other mnemonics in the List box a ESCAPE character (the first character of any mnemonic) was incorrectly handled in some releases of V16.
To the best of our knowledge this was addressed and fixed in 16.20 however long term as a general principal you should avoid using ESC as a column/row separator character in a list box.
Cedric:
I'm using V16.20 on server side... The error is random... Normally, users call me just after the fact, so I rarely see it from my eyes! I've experienced it once last week and it was while loading the main page. That screen is basically just buttons, menus, text and frames. The buttons all have an icon (some are pvx native icons, but some are images (ICO, GIF, BMP, PNG or JPG) stored on the client PC).
Cedric:
Hey guys,
just a quick note that we still struggle with this problem. I'm pretty sure something is wrong in PVX17... I had another customer which was using V11 for a cupple of years without any issues. Now, I have updated their server and Windx to the latest V17.10 and suddenly some users are facing that error (freezes and process stops responding on Client's PC). It's not all users though.... I've noticed that users that had older computers with less RAM and are using Ms Teams has the issue.(it crashes 7-8 times a day) I have disabled MsTeams and rebooted the PC and the problem seemed to have disapeared. Now, not sure if the problem is with MsTeams or just the fact the MsTeams uses lots of Ram ( on a 4Gb Win7 64bits PC ) and causing the issue with PVX. But, the problem wasn't present with V11 though... Anyway, if someone reads this and knows about this, your help would be appreciated!
thanks
Mike King:
Cedric
Its possible that there is a conflict with MS Teams although no one else has reported this.
Its also possible that due to the fact that PxPlus V17 itself uses more memory that V11 could be compounding the issue. Over the past eight years a lot has been added to PxPlus and some of these will increase the amount of memory being used. The EXE itself has grown by almost 25% and the install is almost 3 times the size due to the fact we now provide an integrated Chromium browser, newer TLS1.2 support, ZIP file access, UTF8 support, improved graphic engines and many other product enhancements.
Also MS Teams has a MINIMUM requirement of 4GB -- so if that is what your systems are it leaves very little (if any) for PxPlus.
Navigation
[0] Message Index
[#] Next page
Go to full version