Skip to content
This repository has been archived by the owner on May 6, 2024. It is now read-only.

the app crashed due to the memory issue when i click the course after login successfully #1614

Closed
wanglong121 opened this issue Mar 7, 2022 · 8 comments
Labels
wontfix This will not be worked on

Comments

@wanglong121
Copy link

The page is stuck and cannot load the course details page view, the app crashed after tens of seconds;
openedx base version : open-release-lilac3;

@wanglong121
Copy link
Author

the console output some logs as follows(many similar):
2022-03-07 09:37:15.150586+0800 edX[7971:2119488] [LayoutConstraints] Unable to simultaneously satisfy constraints.
Probably at least one of the constraints in the following list is one you don't want.
Try this:
(1) look at each constraint and try to figure out which you don't expect;
(2) find the code that added the unwanted constraint or constraints and fix it.
(Note: If you're seeing NSAutoresizingMaskLayoutConstraints that you don't understand, refer to the documentation for the UIView property translatesAutoresizingMaskIntoConstraints)
(
"<edX.LayoutConstraint:0x285384a20@CourseCardView.swift#96 UIView:0x1144db0b0.bottom == edX.CourseCardView:0x1144dad10.bottom - 0.5>",
"<edX.LayoutConstraint:0x285384ea0@CourseCardView.swift#121 UIView:0x1144db870.top == edX.CourseCardView:0x1144dad10.top>",
"<edX.LayoutConstraint:0x285384de0@CourseCardView.swift#122 UIView:0x1144db870.bottom == UIView:0x1144db0b0.top>",
"<NSAutoresizingMaskLayoutConstraint:0x2816d3200 edX.CourseCardView:0x1144dad10.height == 0>"
)
Will attempt to recover by breaking constraint
<edX.LayoutConstraint:0x285384a20@CourseCardView.swift#96 UIView:0x1144db0b0.bottom == edX.CourseCardView:0x1144dad10.bottom - 0.5>
Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
......

@mumer92
Copy link
Contributor

mumer92 commented Mar 14, 2022

@wanglong121 this is info log, not the actual crash log, can you add the actual crash log?

@wanglong121
Copy link
Author

@wanglong121 this is info log, not the actual crash log, can you add the actual crash log?

Details

The app “edX” on iPhone quit unexpectedly.
Domain: IDEDebugSessionErrorDomain
Code: 10
Failure Reason: Message from debugger: Terminated due to memory issue
User Info: {
DVTErrorCreationDateKey = "2022-03-15 01:22:45 +0000";
IDERunOperationFailingWorker = DBGLLDBLauncher;
}

Analytics Event: com.apple.dt.IDERunOperationWorkerFinished : {
"device_model" = "iPhone9,1";
"device_osBuild" = "14.7.1 (18G82)";
"device_platform" = "com.apple.platform.iphoneos";
"launchSession_schemeCommand" = Run;
"launchSession_state" = 2;
"launchSession_targetArch" = arm64;
"operation_duration_ms" = 86240;
"operation_errorCode" = 10;
"operation_errorDomain" = IDEDebugSessionErrorDomain;
"operation_errorWorker" = DBGLLDBLauncher;
"operation_name" = IDEiPhoneRunOperationWorkerGroup;
"param_consoleMode" = 0;
"param_debugger_attachToExtensions" = 0;
"param_debugger_attachToXPC" = 1;
"param_debugger_type" = 5;
"param_destination_isProxy" = 0;
"param_destination_platform" = "com.apple.platform.iphoneos";
"param_diag_MainThreadChecker_stopOnIssue" = 0;
"param_diag_MallocStackLogging_enableDuringAttach" = 0;
"param_diag_MallocStackLogging_enableForXPC" = 1;
"param_diag_allowLocationSimulation" = 1;
"param_diag_gpu_frameCapture_enable" = 0;
"param_diag_gpu_shaderValidation_enable" = 0;
"param_diag_gpu_validation_enable" = 0;
"param_diag_memoryGraphOnResourceException" = 0;
"param_diag_queueDebugging_enable" = 1;
"param_diag_runtimeProfile_generate" = 0;
"param_diag_sanitizer_asan_enable" = 0;
"param_diag_sanitizer_tsan_enable" = 0;
"param_diag_sanitizer_tsan_stopOnIssue" = 0;
"param_diag_sanitizer_ubsan_stopOnIssue" = 0;
"param_diag_showNonLocalizedStrings" = 0;
"param_diag_viewDebugging_enabled" = 1;
"param_diag_viewDebugging_insertDylibOnLaunch" = 1;
"param_install_style" = 0;
"param_launcher_UID" = 2;
"param_launcher_allowDeviceSensorReplayData" = 0;
"param_launcher_kind" = 0;
"param_launcher_style" = 0;
"param_launcher_substyle" = 0;
"param_runnable_appExtensionHostRunMode" = 0;
"param_runnable_productType" = "com.apple.product-type.application";
"param_runnable_swiftVersion" = "5.5.2";
"param_runnable_type" = 2;
"param_testing_launchedForTesting" = 0;
"param_testing_suppressSimulatorApp" = 0;
"param_testing_usingCLI" = 0;
"sdk_canonicalName" = "iphoneos15.2";
"sdk_osVersion" = "15.2";
"sdk_variant" = iphoneos;
}

System Information

macOS Version 12.2.1 (Build 21D62)
Xcode 13.2.1 (19586) (Build 13C100)
Timestamp: 2022-03-15T09:22:45+08:00

@wanglong121
Copy link
Author

@wanglong121 this is info log, not the actual crash log, can you add the actual crash log?

the console has no more crash log, Do i have any problem compile with xcode 13.2.1 ?

@mumer92
Copy link
Contributor

mumer92 commented Mar 15, 2022

@wanglong121

  1. Are you using latest code from master? if so, it requires Xcode 13.2.1.
    if you are using the last release code, you will need Xcode 12.5.1

  2. Is it happening on vanilla installation of code? or do you have some modifications done?

  3. Can you please check for memory leaks using Xcode's Allocations tools and also look for leak objects.

@wanglong121
Copy link
Author

wanglong121 commented Mar 16, 2022

@mumer92
thanks for your reply!
1、I'm using the open release code :open-release-lilac3, compile it with xcode 13.2.1;
2、it is happening on vanilla installation of code
3、I‘m try to use Xcode's Allocations tools to find the leak objects, I will reply you latter.

@wanglong121
Copy link
Author

wanglong121 commented Mar 16, 2022

1

I find the place which maybe the problem occurr, as shown above. Can you find the cause of it? I need some guidance。

@mumer92
Copy link
Contributor

mumer92 commented Mar 17, 2022

@wanglong121 can you share recording of the app? from the logs, is looks like it is crashing somewhere in scope of UITableView.

@kdmccormick kdmccormick added the wontfix This will not be worked on label May 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants