alexpevzner
commented
2 years ago Hi @EMlyDinEsHMG !
I will look to this problem.
Closed EMlyDinEsHMG closed 12 months ago
alexpevzner
commented
2 years ago Hi @EMlyDinEsHMG !
I will look to this problem.
alexpevzner
commented
2 years ago Hi @EMlyDinEsHMG,
Go programs' executable size is huge, because Go always links everything statically. It makes virtual memory consumption to be large. But is is only the virtual address space, not the real memory, Actual memory consumption, indicated by RSS, depends on program behaviour and for ipp-usb is not very large (less that for the ippusbxd, for example).
So for now, I don't see that ipp-usb causes any real problem.
EMlyDinEsHMG
commented
2 years ago Hi! @alexpevzner
Thanks for the response. Is there any estimate like how much ipp-usb will take if only one external USB printer is connected for printing, and used? Also we have one concern that is there requirement from ipp-usb requiring contiguous memory (how much if its) ? As we are thinking it could be due to memory fragmentation as well.
Please share your side insight about ipp-usb we have requested above (even we have attached logs of kernel backtrace) so that we can root cause the issue.
Thanks
EMlyDinEsHMG
commented
1 year ago Hi!
Thanks for your response. As you mentioned actual resident memory will depend on behaviour, what could be the max rss usage we can expect if we use single printer?
Thanks
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Alexander Pevzner @.> Sent: Saturday, March 12, 2022 6:49:38 PM To: OpenPrinting/ipp-usb @.> Cc: EMlyDinEsHMG @.>; Mention @.> Subject: Re: [OpenPrinting/ipp-usb] OOM triggered due to high virtual memory usage by ipp-usb (Issue #43)
Hi @EMlyDinEsHMGhttps://github.com/EMlyDinEsHMG,
Go programs' executable size is huge, because Go always links everything statically. It makes virtual memory consumption to be large. But is is only the virtual address space, not the real memory, Actual memory consumption, indicated by RSS, depends on program behaviour and for ipp-usb is not very large (less that for the ippusbxd, for example).
So for now, I don't see that ipp-usb causes any real problem.
— Reply to this email directly, view it on GitHubhttps://github.com/OpenPrinting/ipp-usb/issues/43#issuecomment-1065882383, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AASUMHOJCAQOLPGFJ2DZKTTU7SKWVANCNFSM5QRQDFLA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>
alexpevzner
commented
12 months ago Looks like issue is outside of this project scope...
Hi!
We are using ipp-usb in our yocto based linux in arm platform for providing external printing feature using ipp protocol. It was working fine with HP printers(other brands have issues either not being detected or not responding to ipp req). Recently we have been seeing oom killer getting triggered in our device. When we check the back trace, we have found one observation is that ipp-usb vm memory is really high compared to available in RAM so we wanted to understand, and clarify if there is any issue. We have only 512MB RAM without swap. I am attaching the back trace we got from kernel log for the oom killing. Please check, and share if there any issue from ipp-usb with respect to vm usage (though rss memory is not high). We are using latest ipp-usb available which 0.9.19-2.
Please any help would be really appreciated from these logs.
Thanks PS: Let me know if anything else is required.