Debug.log size limit

Hi all,

I am doing a massive number of tests with Katalon Studio and noticed that the debug.log of the project in-use is becoming HUGE, with 700 MB already.

My question:
Is there anyway to put a size limit to the logs, debug.log specifically?

Thanks in advance.
Best Regards

Take a look at these settings:

And read this help topic:

1 Like

Hi @Russ_Thomas,

I’ve already looked into it but sincerely, it didn’t help because I want to keep the log configurations as it is right now.
What I want to confirm if there is any other way to limit log file sizes, either via prompt, menu config or in log.properties parameters.

Are you able to confirm this?

Thanks in advance.
Best Regards

Actually, I don’t think I understand the issue. Let’s try these guys…

@ThanhTo @duyluong @Brandon_Hein @kazurayam

You can significantly decrease the size of the log by disabling logging executed steps.

Log executed test steps
Starting from Katalon Studio version 7.0 , an option to disable Log executed test steps is available in Project Settings > Executions . By enabling or disabling this option, you can decide whether the logs include executed test steps or not.
By disabling logging executed step, you should be able to decrease the size of the log overall.

However, … see Project Settings > Executions > Enable/Disable logging executed steps; is it deprecated?

1 Like

@joao.alves

I think there is no way to set that digit.

How do you want Katalon Studio to behave when the log file size comes up to the limit you set? Do you want Katalon Studio intentionally crash? Or do you want Katalon Studio continue running without logging any longer? To me, both look undesirable.

I think you should try to make the log less verbose and decrease the size of log by configuring logs by some methods proposed in

1 Like

I think this would need to be handled in the KS application code. The log.properties just exposes some settings publicly, but not all.

KS uses slf4j from what I can tell. One way to do this in slf4j is to create “rolling” logs, where you define a max file size, and the logs “roll” within that size (i.e. a FIFO configuration). This is done by using the RollingFileAppender instead of the usual FileAppender. See this discussion:

Long story short, I don’t believe this is something you can configure yourself.

I’m more curious about what could be blowing those logs up so much… Can you give us a snippet of the debug.log file? We have a relatively large project as well, but our debug.log is sitting at ~100k.

3 Likes

Hold on !

What is debug.log here?

I am confused. I have never seen a file named debug.log in any of Katalon Studio projects. I use Katalon Studio version 7.2.1 now.

If the debug.log is something your script creates for itself = Katalon Studio has nothing to do with it, then all the comments I wrote above are completely out of the point.

Or debug.log is something newly introduced by newer Katalon Studio than version 7.2.1?

Agreed. I assume we’re talking about the regular .log file.

Unless something else is specified here?

image

Mine appears in the project directory:

1 Like

What triggers it?

That I’m not sure, maybe @ThanhTo can clarify. I honestly never look at this file. Here’s an example of what’s logged there in mine:

[1010/174038.520:ERROR:process_memory_win.cc(73)] ReadMemory at 0x4e5c000 of 560 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[1010/174038.932:ERROR:process_snapshot_win.cc(389)] ReadMemory PEB
[1010/174038.932:ERROR:process_memory_win.cc(73)] ReadMemory at 0xc0000 of 64 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[1010/174038.932:WARNING:pe_image_reader.cc(340)] could not read dos header from C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[1010/174038.932:ERROR:process_memory_win.cc(73)] ReadMemory at 0xc0000 of 64 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[1010/174038.932:WARNING:pe_image_reader.cc(340)] could not read dos header from C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[1010/174038.932:ERROR:process_memory_win.cc(73)] ReadMemory at 0x77560000 of 64 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[1010/174038.932:WARNING:pe_image_reader.cc(340)] could not read dos header from C:\Windows\SYSTEM32\ntdll.dll
[1010/174038.932:ERROR:process_memory_win.cc(73)] ReadMemory at 0x77560000 of 64 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[1010/174038.932:WARNING:pe_image_reader.cc(340)] could not read dos header from C:\Windows\SYSTEM32\ntdll.dll
[1010/174038.933:ERROR:process_memory_win.cc(73)] ReadMemory at 0x76370000 of 64 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[1010/174038.933:WARNING:pe_image_reader.cc(340)] could not read dos header from C:\Windows\System32\KERNEL32.DLL
[1010/174038.933:ERROR:process_memory_win.cc(73)] ReadMemory at 0x76370000 of 64 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[1010/174038.933:WARNING:pe_image_reader.cc(340)] could not read dos header from C:\Windows\System32\KERNEL32.DLL
[1010/174038.933:ERROR:process_memory_win.cc(73)] ReadMemory at 0x75880000 of 64 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[1010/174038.933:WARNING:pe_image_reader.cc(340)] could not read dos header from C:\Windows\System32\KERNELBASE.dll
[1010/174038.933:ERROR:process_memory_win.cc(73)] ReadMemory at 0x75880000 of 64 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[1010/174038.933:WARNING:pe_image_reader.cc(340)] could not read dos header from C:\Windows\System32\KERNELBASE.dll

Googling with keywords “chrome debug.log” showed me some URL which talks about debug.log.

One of the post I happened to find:

tells that debug.log is created by Google Chrome browser, is a internal debug logging. Some particular version of Chrome emits huge amount of debug prints. Upgrading Chrome to newer version may stop it.

Hi guys,

Sorry for the late response and thanks for all the inputs!

In fact, I am managing a Katalon project (in the 6.3.3 app version) that was not originally created by me.
Nevertheless, I am not aware how Chrome can be related with debug.log creation since I don’t use the browser in the machine where I have Katalon installed.

debug.log as shown above, it reflects at least all the execution log. Not user what triggers it, if it is every call within the run process or not (it seems so).
Regarding the log.properties, there is nothing declared in there.
I even restarted the app several times and the debug.log does not have any kind of housekeeping. Thus, it is never reset or archived.

Hope it helps you to help me understand.

Best Regards

As I mentioned,

Brandon_Hein showed his debug.log file. In there we could see a few lines of

[1010/174038.932:WARNING:pe_image_reader.cc(340)] could not read dos header from 
    C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

This line indicates that his debug.log is related to chrome.exe. This is the reason why I started talking about Chrome browser.

Have you read the content of debug.log file? Could you copy && and paste here the top 100 lines of your debug.log file?