Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (7)

Resolved kernelbase.dll crash - PB2017R3

  1. Issue
0
Votes
Undo
  1. David Peace (Powersoft)
    David Peace (Powersoft)
  2. PowerBuilder
  3. Monday, 20 January 2020 11:43 AM UTC

Hi Guys

I'm getting a not so random crash from our newly migrated application to pb2017r3 as follows:

Faulting application name: tstravel.exe, version: 5.0.17.0, time stamp: 0x5df05d07
Faulting module name: KERNELBASE.dll, version: 6.1.7601.24545, time stamp: 0x5e0eb7f5
Exception code: 0xc0000005
Fault offset: 0x0000c5af
Faulting process id: 0x20b0
Faulting application start time: 0x01d5cf82cf155910
Faulting application path: C:\Powersoft\tstravel\tstravel.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 2c898470-3b76-11ea-885b-989096a8952d

Followed by 30 seconds later:

Fault bucket 1630458091, type 493030608
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: tstravel.exe
P2: 5.0.17.0
P3: 5df05d07
P4: KERNELBASE.dll
P5: 6.1.7601.24545
P6: 5e0eb7f5
P7: c0000005
P8: 0000c5af
P9:
P10:

Attached files:
C:\Users\dpeace\AppData\Local\Temp\WER9A5E.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\dpeace\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_tstravel.exe_67cf1f9c3064cdd06bbe29a21f4fb437c6184e6_152514ab

Analysis symbol:
Rechecking for solution: 0
Report Id: 2c898470-3b76-11ea-885b-989096a8952d
Report Status: 0

I also noticed a file in my user temp called .DVP-WIN7A.dpeace.log.ERROR.log20200120-111628.8544

In this file was the following:

Log file created at: 2020/01/20 11:16:28
Running on machine: DVP-WIN7A
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0120 11:16:28.943296  7192 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info

What on earth is that all about!?

It seems too much of a coinsidence that this file appeared about the time the system crashed.

Any thoughts on here foot-in-mouth

 

  1. Crash
  2. PowerBuilder
Is there a datawindow expression to test for Colum...
ConnectToNewObject("ADODB.Connection") doesn't wor...
Accepted Answer
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 13:46 PM UTC
  2. PowerBuilder
  3. # Permalink

Seems to be a known bug:
https://www.appeon.com/standardsupport/track/view?id=2737

Here's more:
https://community.appeon.com/index.php/qna/q-a/powerbuilder-2019-2082-crashes-when-i-m-working-with-a-datawindow-and-computed-field

Comment
Load more comments
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 20 January 2020 14:20 PM UTC
I agree, appeon might ask for a "small sample app to reproduce the problem", but still it won't hurt to ask if there's any outcome on their still outstanding bug on similar topic.

At least it's consistent and fails the second time you run it.

Have you thought about running processmonitor on it?



Good Luck, this seems to be a tough one!
  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 20 January 2020 14:38 PM UTC
Thanks for your enthisiastic help, I'm still looking for the peice of bad code that is causing my problem, been like this for nearly 10 years now.....

I definately think that the fake file stuff is related to PB crashing and not the crash itself. If PB closes normall this is cleaned up.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 20 January 2020 15:22 PM UTC
YW David, I know you're very experienced, so I don't think you'd need any help with the Email and OLE. We have it all working, but slowly are starting to look at other solutions like ms-graph for office 365 and personally I like "MailKit" as a promising solution.
  1. Helpful
There are no comments made yet.
Responses (7)
Danish Ahamed LiakathAli
Danish Ahamed LiakathAli Accepted Answer Pending Moderation
  1. Tuesday, 8 September 2020 20:55 PM UTC
  2. PowerBuilder
  3. # 1

Hi David,

            Have you got any solution for this issue. I am facing the same issue after migrate  to  2019 R2 . I have added a .XLSX export option. when exporting any data using GetFileSaveName and dw.SaveAs() method. I am able to export the data and save the file  with .XLSX extension after 2 mins the application gets crashed. Working fine when running from the source. same code works fine in small app that I created

Comment
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Wednesday, 9 September 2020 08:54 AM UTC
Unfortunately I cannot remember the exact details. I found it was caused by a peice if invalid syntax and a DW or DS statement, one of the parameters was incorrect or missing. The compiler was not picking this up. I fixed the code and it resolved the problem.



I found the problem by adding debug logging to identify the statement that caused the crash. When I looked at the code it stood out like a sore thumb.



Hope that helps.



David
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 17:15 PM UTC
  2. PowerBuilder
  3. # 2

Hi David;

  This could also be caused if the files your PB App are using are very large. Then you would need to use the FileLength64() command vs the FileLength() PB command to get the correct values for subsequent processing.

Regards ... Chris

Comment
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 20 January 2020 17:23 PM UTC
Hi Chris



I have traced the error down to the mailsession object mailLogon function. It crashes at that line of code. I've tried to reproduce the problem in a simple test case but no luck so far.



My senario is:

Mail UO Created

Email constructed

Email logon

Email successfully sent

Email logoff

Email UO destroyed



Repeat the above and the logon crashes PB runtime. A simple test case does not fail.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Monday, 20 January 2020 17:59 PM UTC
Hi David;

FYI: I just looked through all the tickets which register "KERNELBASE" dll being related to the issue. That only produced 11 tickets in total form the ticket system. None of these 11 tickets for that DLL were related to emailing.

Regards ... Chris
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 14:26 PM UTC
  2. PowerBuilder
  3. # 3

Have you tried distributing all of the runtime libraries? (though then it wouldn't make sense that it works the first time you run it).

Another wild guess: could it be some file is staying locked (longer than necessary) after having run the first time?

 

Comment
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 20 January 2020 14:43 PM UTC
We've had all sorts of ideas like that... that was until we realised that running the process twice caused the problem.



At the moment it looks like the process gets called twice the second time yu run it, if you nsee what I mean? The whole procedure from the menu button being clicked is running through completely and then immediately starting again. The other wild card is that the crash occurs when it tries ot send an email, another windup becuase of the Extended Mapi debarkle. I thought it was something to do with that, and it way well be yet!
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 20 January 2020 15:19 PM UTC


Okay, so what I would do is then first run the whole process, but without the email stuff.

As far as extended mapi is concerned, I noticed a changed behaviour between pb 12.6 and higher, considering the pb.ini setting: https://www.appeon.com/standardsupport/search/view?id=3506

(We use mapi only to show the address book (since that window pops up nicely), all the rest we do it with OLE against Outlook, since even when you use MAPI for the send, you will still have to "flush" the outbox using OLE to make sure the email doesn't get stuck in there. Supposedly the extendedmapi setting 'No' would solve that problem, but setting it to "No" makes other bugs appear, especially with the Addressbook, so for us it has to stay on 'Yes' only for versions after pb12.6).

Sorry I cannot be of any more help, that's about all of my ideas.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 13:53 PM UTC
  2. PowerBuilder
  3. # 4

Can your check the access right on the folder where "C:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info" resides?

Check if the file (when existing) doesn't have a 0 byte filesize?

Maybe run "as administrator"?

Just trying to give any ideas. Hope someone solves it.

Comment
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 20 January 2020 14:06 PM UTC
A normal user has read & execute but no write, which is what you would expect under program files
  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 20 January 2020 14:21 PM UTC
Runas administrator did not change anything, thankfully :)
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 13:18 PM UTC
  2. PowerBuilder
  3. # 5

Ha ! 

I knew I saw that one before!

https://www.appeon.com/standardsupport/search/view?id=1435

 

Comment
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 20 January 2020 13:34 PM UTC
That's about the IDE crashing on a full build. My crash is in a production .exe, when a user does certain things.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 20 January 2020 13:46 PM UTC
Yes, but coincidentally it's in the same file and the same line number.

  1. Helpful
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 20 January 2020 14:14 PM UTC
Perhaps its the crash that is causing that file to be written, in other words a secondary problem.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 20 January 2020 13:16 PM UTC
  2. PowerBuilder
  3. # 6

Hi David,

I've seen that GetFileLength error some time before ...

You forgot to attach the mentioned files?

regards,

migueL

Comment
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 20 January 2020 13:35 PM UTC
The only file I could find was a Report.wer, this contains.....



Version=1

EventType=APPCRASH

EventTime=132239925338079031

ReportType=2

Consent=1

UploadTime=132239925339639161

ReportIdentifier=2c898471-3b76-11ea-885b-989096a8952d

IntegratorReportIdentifier=2c898470-3b76-11ea-885b-989096a8952d

WOW64=1

Response.BucketId=1630458091

Response.BucketTable=493030608

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=tstravel.exe

Sig[1].Name=Application Version

Sig[1].Value=5.0.17.0

Sig[2].Name=Application Timestamp

Sig[2].Value=5df05d07

Sig[3].Name=Fault Module Name

Sig[3].Value=KERNELBASE.dll

Sig[4].Name=Fault Module Version

Sig[4].Value=6.1.7601.24545

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=5e0eb7f5

Sig[6].Name=Exception Code

Sig[6].Value=c0000005

Sig[7].Name=Exception Offset

Sig[7].Value=0000c5af

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.256.48

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=2057

DynamicSig[22].Name=Additional Information 1

DynamicSig[22].Value=9aac

DynamicSig[23].Name=Additional Information 2

DynamicSig[23].Value=9aacf3bbda9fbfc338ab41349ed201f1

DynamicSig[24].Name=Additional Information 3

DynamicSig[24].Value=3fb1

DynamicSig[25].Name=Additional Information 4

DynamicSig[25].Value=3fb110d647e35db9690c394e426f2148

UI[2]=C:\Powersoft\tstravel\tstravel.exe

UI[3]=TSTRAVEL has stopped working

UI[4]=Windows can check online for a solution to the problem.

UI[5]=Check online for a solution and close the program

UI[6]=Check online for a solution later and close the program

UI[7]=Close the program

LoadedModule[0]=C:\Powersoft\tstravel\tstravel.exe

LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll

LoadedModule[2]=C:\Windows\syswow64\kernel32.dll

LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll

LoadedModule[4]=C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBVM170.dll

LoadedModule[5]=c:\powersoft\shared\libjcc.dll

LoadedModule[6]=c:\powersoft\shared\libjutils.dll

LoadedModule[7]=C:\Windows\syswow64\MSVCRT.dll

LoadedModule[8]=c:\powersoft\shared\nlwnsck.dll

LoadedModule[9]=c:\powersoft\shared\libjtml.dll

LoadedModule[10]=C:\Windows\system32\WSOCK32.dll

LoadedModule[11]=C:\Windows\syswow64\WS2_32.dll

LoadedModule[12]=C:\Windows\syswow64\RPCRT4.dll

LoadedModule[13]=C:\Windows\syswow64\SspiCli.dll

LoadedModule[14]=C:\Windows\syswow64\CRYPTBASE.dll

LoadedModule[15]=C:\Windows\SysWOW64\sechost.dll

LoadedModule[16]=C:\Windows\syswow64\NSI.dll

LoadedModule[17]=C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBUIS170.dll

LoadedModule[18]=C:\Windows\syswow64\USER32.dll

LoadedModule[19]=C:\Windows\syswow64\GDI32.dll

LoadedModule[20]=C:\Windows\syswow64\LPK.dll

LoadedModule[21]=C:\Windows\syswow64\USP10.dll

LoadedModule[22]=C:\Windows\syswow64\ADVAPI32.dll

LoadedModule[23]=C:\Windows\system32\MSIMG32.dll

LoadedModule[24]=C:\Windows\syswow64\COMDLG32.dll

LoadedModule[25]=C:\Windows\syswow64\SHLWAPI.dll

LoadedModule[26]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\COMCTL32.dll

LoadedModule[27]=C:\Windows\syswow64\SHELL32.dll

LoadedModule[28]=C:\Windows\system32\WINSPOOL.DRV

LoadedModule[29]=C:\Windows\syswow64\ole32.dll

LoadedModule[30]=C:\Windows\syswow64\OLEAUT32.dll

LoadedModule[31]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.24542_none_5c0717c7a00ddc6d\gdiplus.dll

LoadedModule[32]=C:\Windows\system32\OLEACC.dll

LoadedModule[33]=C:\Windows\syswow64\IMM32.dll

LoadedModule[34]=C:\Windows\syswow64\MSCTF.dll

LoadedModule[35]=C:\Windows\system32\WINMM.dll

LoadedModule[36]=C:\Program Files (x86)\Appeon\Shared\PowerBuilder\PBSHR170.dll

LoadedModule[37]=C:\Windows\system32\MSVCR100.dll

LoadedModule[38]=C:\Windows\system32\dwmapi.dll

LoadedModule[39]=C:\Windows\system32\MSVCP100.dll

LoadedModule[40]=C:\Windows\system32\VERSION.dll

LoadedModule[41]=C:\Windows\system32\oledlg.dll

LoadedModule[42]=C:\Windows\system32\UxTheme.dll

LoadedModule[43]=C:\Windows\system32\ATL100.DLL

LoadedModule[44]=C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbjson170.dll

LoadedModule[45]=C:\Windows\syswow64\CRYPT32.dll

LoadedModule[46]=C:\Windows\syswow64\MSASN1.dll

LoadedModule[47]=C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbdwe170.dll

LoadedModule[48]=C:\Windows\system32\Wtsapi32.dll

LoadedModule[49]=C:\Windows\system32\WINSTA.dll

LoadedModule[50]=C:\Windows\system32\WindowsCodecs.dll

LoadedModule[51]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.24483_none_2b200f664577e14b\comctl32.DLL

LoadedModule[52]=C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbORA170.dll

LoadedModule[53]=c:\oracle\product\11.2.0\client_1\OCI.DLL

LoadedModule[54]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6229_none_d089f796442de10e\MSVCR80.dll

LoadedModule[55]=C:\Windows\syswow64\PSAPI.DLL

LoadedModule[56]=c:\oracle\product\11.2.0\client_1\OraOCIEI11.dll

LoadedModule[57]=C:\Windows\system32\iphlpapi.dll

LoadedModule[58]=C:\Windows\system32\WINNSI.DLL

LoadedModule[59]=C:\Windows\system32\Secur32.dll

LoadedModule[60]=C:\Windows\system32\dbghelp.dll

LoadedModule[61]=C:\Windows\system32\CRYPTUI.dll

LoadedModule[62]=C:\Windows\system32\mswsock.dll

LoadedModule[63]=C:\Windows\System32\wship6.dll

LoadedModule[64]=C:\Windows\syswow64\profapi.dll

LoadedModule[65]=C:\Windows\system32\NLAapi.dll

LoadedModule[66]=C:\Windows\system32\napinsp.dll

LoadedModule[67]=C:\Windows\system32\pnrpnsp.dll

LoadedModule[68]=C:\Windows\system32\DNSAPI.dll

LoadedModule[69]=C:\Windows\System32\winrnr.dll

LoadedModule[70]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL

LoadedModule[71]=C:\Windows\System32\wshtcpip.dll

LoadedModule[72]=C:\Windows\system32\rasadhlp.dll

LoadedModule[73]=C:\Windows\System32\fwpuclnt.dll

LoadedModule[74]=C:\Windows\system32\wkscli.dll

LoadedModule[75]=C:\Windows\system32\cscapi.dll

LoadedModule[76]=c:\powersoft\shared\canvas.pbx

LoadedModule[77]=C:\Program Files (x86)\Appeon\Shared\PowerBuilder\pbtctext170.dll

LoadedModule[78]=C:\Program Files (x86)\Appeon\Shared\PowerBuilder\TER25.DLL

LoadedModule[79]=C:\Program Files (x86)\Appeon\Shared\PowerBuilder\SSGP.DLL

LoadedModule[80]=C:\Windows\system32\apphelp.dll

LoadedModule[81]=C:\Windows\syswow64\CLBCatQ.DLL

LoadedModule[82]=C:\Windows\system32\prnfldr.dll

LoadedModule[83]=C:\Windows\system32\PROPSYS.dll

LoadedModule[84]=C:\Windows\system32\slc.dll

LoadedModule[85]=C:\Windows\system32\mscms.dll

LoadedModule[86]=C:\Windows\syswow64\USERENV.dll

LoadedModule[87]=C:\Windows\SysWOW64\SFC.DLL

LoadedModule[88]=C:\Windows\system32\sfc_os.DLL

LoadedModule[89]=C:\Program Files (x86)\Microsoft Office\Office15\olmapi32.dll

LoadedModule[90]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll

LoadedModule[91]=C:\Windows\system32\msi.dll

LoadedModule[92]=C:\Program Files (x86)\Microsoft Office\Office15\1033\mapir.dll

LoadedModule[93]=C:\Windows\system32\ntmarta.dll

LoadedModule[94]=C:\Windows\syswow64\WLDAP32.dll

LoadedModule[95]=C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\riched20.dll

LoadedModule[96]=C:\Program Files (x86)\Microsoft Office\Office15\contab32.dll

LoadedModule[97]=C:\Windows\system32\d2d1.dll

LoadedModule[98]=C:\Windows\system32\dxgi.dll

LoadedModule[99]=C:\Windows\syswow64\WINTRUST.dll

LoadedModule[100]=C:\Windows\system32\DavClnt.DLL

LoadedModule[101]=C:\Windows\system32\DAVHLPR.dll

LoadedModule[102]=C:\Program Files (x86)\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\osppc.dll

LoadedModule[103]=C:\Program Files (x86)\Microsoft Office\Office15\EMSMDB32.DLL

LoadedModule[104]=C:\Windows\System32\netprofm.dll

LoadedModule[105]=C:\Windows\system32\CRYPTSP.dll

LoadedModule[106]=C:\Windows\system32\rsaenh.dll

LoadedModule[107]=C:\Windows\system32\RpcRtRemote.dll

LoadedModule[108]=C:\Windows\System32\npmproxy.dll

LoadedModule[109]=C:\Windows\system32\dhcpcsvc6.DLL

LoadedModule[110]=C:\Windows\system32\dhcpcsvc.DLL

LoadedModule[111]=C:\Windows\system32\NTDSAPI.dll

LoadedModule[112]=C:\Windows\system32\credssp.dll

LoadedModule[113]=C:\Windows\SysWOW64\Kerberos.DLL

LoadedModule[114]=C:\Windows\system32\cryptdll.dll

LoadedModule[115]=C:\Windows\system32\bcrypt.dll

LoadedModule[116]=C:\Windows\SysWOW64\bcryptprimitives.dll

LoadedModule[117]=C:\Users\dpeace\AppData\Local\Microsoft\OneDrive\19.222.1110.0006\FileSyncShell.dll

LoadedModule[118]=C:\Windows\syswow64\WININET.dll

LoadedModule[119]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll

LoadedModule[120]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll

LoadedModule[121]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll

LoadedModule[122]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll

LoadedModule[123]=C:\Windows\syswow64\normaliz.DLL

LoadedModule[124]=C:\Windows\syswow64\iertutil.dll

LoadedModule[125]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll

LoadedModule[126]=C:\Windows\system32\api-ms-win-core-synch-l1-2-0.DLL

LoadedModule[127]=C:\Users\dpeace\AppData\Roaming\Dropbox\bin\DropboxExt.27.0.dll

LoadedModule[128]=C:\Windows\syswow64\SETUPAPI.dll

LoadedModule[129]=C:\Windows\syswow64\CFGMGR32.dll

LoadedModule[130]=C:\Windows\syswow64\DEVOBJ.dll

LoadedModule[131]=C:\Windows\SysWOW64\thumbcache.dll

LoadedModule[132]=C:\Windows\SysWOW64\PhotoMetadataHandler.dll

State[0].Key=Transport.DoneStage1

State[0].Value=1

State[1].Key=DataRequest

State[1].Value=Bucket=1630458091/nBucketTable=493030608/nResponse=1/n

FriendlyEventName=Stopped working

ConsentKey=APPCRASH

AppName=TSTRAVEL

AppPath=C:\Powersoft\tstravel\tstravel.exe

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.