Failed to save log file
Opened this issue · 3 comments
I'm receiving the following error when trying to reproduce a crash log generated by grinder:
[-D-] Error, unable to save the log file 'C:\Users\test\AppData\Local\Temp\L
ow\logger_14256.xml' (File doesnt exist)
[-D-] Failed to save the log file.
[*D*]
[*D*] Caught a Write Access Violation in process 14256 at 2017-05-02 02:55:01 with a crash hash of 91245474.AAFA6CDF
[*D*] Posted crash to '172.16.56.147/grinder-server/status.php'
Updated with the following issues:
[+D+] Attached debugger to new 32-bit process 7772.
[+D+] JavaScriptCore.dll DLL loaded into process 7772 at address 0x69320000
[-D-] Unable to hook JavaScript parseFloat() in process 7772, logger dll not inj
ected.
[+D+] JavaScriptCore.dll DLL loaded into process 7772 at address 0x69320000
[-D-] Unable to hook JavaScript parseFloat() in process 7772, logger dll not inj
ected.
[+D+] JavaScriptCore.dll DLL loaded into process 7772 at address 0x69320000
[-D-] Unable to hook JavaScript parseFloat() in process 7772, logger dll not inj
ected.
[+D+] Logger DLL loaded into process 7772 @ 0x731F0000
[+D+] Logging process 7772 to log file 'C:\Users\test\AppData\Local\Temp\Low
\logger_7772.xml'
[+D+] JavaScriptCore.dll DLL loaded into process 7772 at address 0x69320000
[+D+] Resolved JavaScriptCore!parseFloat @ 0x69438100
[+D+] Hooked JavaScript parseFloat() to grinder_logger.dll via proxy @ 0x003F000
0
[+D+] Debug message from process 7772: Safari
[-D-] Error, unable to save the log file '' (can't convert nil into String)
[-D-] Failed to save the log file.
[*D*]
[*D*] Caught a Read Access Violation in SF process 7772 at 2017-05-04 05:46:40 with a crash hash of 557B44B1.557B44B1
[*D*] Posted crash to '172.16.56.148/grinder-server/status.php'
It appears the logger is not correctly writing to disk. I've seen the closed tickets but those fixes did not solve my issue, any thoughts?
Thank you
also the same error for me.
[-D-] Error, unable to save the log file '' (no implicit conversion of nil into String)
[-D-] Failed to save the log file.
[D]
[D] Caught a Read Access Violation in IE11 process 9740 at 2017-05-04 23:50:26 with a crash hash of 27CFCEF8.1E839C32
is there any solution for this?
thx
Not sure, although I'm still looking into it. Will update if I find anything. Hopefully someone else can point us in the right direction.
@stephenfewer any thoughts?