search

fsquillace / junest

The lightweight Arch Linux based distro that runs, without root privileges, on top of any other Linux distro.
GNU General Public License v3.0
2.1k stars 110 forks source link

Question: Memory space utilisation / de-duplication within JuNest environments? #256

Closed abraunegg closed 4 years ago

abraunegg commented 4 years ago

Hi all,

I was wondering if the JuNest folk can provide some insight / analysis on the following issue - https://github.com/abraunegg/onedrive/issues/1086

I am the developer / maintainer for the Linux OneDrive client and the above issue has been raised by a user, who is having an issue - however I am at present unable to replicate not only the issue, but operating environment as well.

The key to understanding the issue / problem is in the debug log files.

In the logs, we have a variable (idToQuery) set to a particular item. that variable is then used, twice, for 2 different queries, with zero variable modification. For the first query, this works without issue, for the second, this variable has been 'munged' & contains bad data - this the query that utilises this query fails.

We have tried using 2 different compilers (DMD / LDC) and the issue remains the same - in the same spot.

This issue is 100% reproducible on the users environment, but, on Arch Linux (or any other Linux platform that is non JuNest) there is zero issue - unable to reproduce at all.

It would be great to get some insight / ideas from the JuNest community on this issue. Does JuNest use any sort of aggressive in-memory deduplication or anything along those lines?

abraunegg commented 4 years ago

Closing this issue as https://github.com/abraunegg/onedrive/issues/1086 is closed ... this is an issue with JuNest that needs to be investigated on the users platform.