-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SCT tool will generate large memory fragment after SCT completion and clicking Test Report Generator. (Bugzilla Bug 4500) #232
Comments
Comment 21714Date: 2023-07-13 22:15:50 +0000
Created attachment 1382 When we complete SCT and then click "Test Report Generator" to generate report, system will generate large memory fragment which will prevent system from boot to Windows directly with the behavior above Attachment: BZ-1382-memory map before generating report.txt |
Comment 21715Date: 2023-07-13 22:16:08 +0000 Created attachment 1383 Attachment: BZ-1383-memory map after generating report.txt.txt |
Comment 22519Date: 2024-02-04 13:56:02 +0000 Hi Zhou, Thank you for reporting this issue. A comment: SCT is a complex suite, and it exercise memory map throughout its execution (not only while generating report). This issue may be complex to analyze and solve. It was not pursued further then. Do you have any real use-case to boot Windows soon after SCT? |
Comment 22523Date: 2024-02-04 22:06:40 +0000 Hi Edhay, If we do not generate report for SCT, the system could boot into Windows soon as normal. |
Comment 22748Date: 2024-03-07 09:28:12 +0000 Hi Zhou, How does this process prevent the windows from booting? Is an exception generated? From your results its clear that Generate Test Results is causing the OS boot to fail. |
Comment 22750Date: 2024-03-08 00:47:33 +0000 Hi Edhay, I think it is the issue of SCT tool and I do not have any solution about that. |
Comment 23380Date: 2024-09-05 10:19:07 +0000 Update on 5th Sept 2024 Lenovo has coding standards to uncover similar issues (allocateBuffer and freeBuffer). |
This issue was created automatically with bugzilla2github
Bugzilla Bug 4500
Date: 2023-07-13T22:15:50+00:00
From: zhouyf12
To: unassigned <>
CC: edhaya.chandran
Last updated: 2024-09-05T10:19:07+00:00
The text was updated successfully, but these errors were encountered: