XYplorer Beta Club

FeedBack for Admin :

I "finally" got an error message !

I just moved two files to a folder,
and when an auto-refresh was due
XY did not crash - but I got this error message :

Error: 14 (0x0000000E)
Desc: Out of string space
Dll: 0
Proc: DB@290, sPathDisplayOrig=C:\Portable\zzz Xtra\zz1\, sPathDisplay=C:\Portable\zzz Xtra\zz1\, sPathReal=C:\Portable\zzz Xtra\zz1\, fPathNotFound=False

Source: XYplorer
XY ver: XYplorer 26.40.0006 - Lifetime License Enterprise
OS: Windows 10 Single Language, 64-bit, Version 20H2, Build 19042.1165 (10.0)
Locale: 1033 (en-US)
ANSI: 1252, ACP: 1252 (ANSI - Latin I)
Font: Verdana 10.5, Verdana 9.75, DBCS: No
DPI: 96 (100%), 1600x900

Date: 2024-09-15 06:53:18

The slightly strange thing is that the path quoted above as
"C:\Portable\zzz Xtra\zz1\"
was on the right pane - which was inactive;
when the error happened, I was working on the left pane
where the address was
"C:\Users\User\Documents"
and it is HERE that I moved the two files to a (sub-)folder
when the error occurred.

In other words, the error is referring
to the inactive pane (I was not working on it).
Strange (to me at least) !

Irrelevant notice on the side :
the weird looking path
"C:\Portable\zzz Xtra\zz1\"
I was using just temporarily
to sort out some files and folders
but it does contain a LOT of files and folders
(challenge for updating paths & contents ?).

Thanks. Unfortunately "Out of string space" is one of those bogus error messages that don't tell the truth but are themselves a victim of some deeper error. Otherwise the error would be 100% reproducible. And for a real "Out of string space" error you need about 100MB text data to copied around in RAM.

Thanks, Admin !

You mentioned RAM, and something that sounds like a strain on RAM.
I am using one of those "RAM cleaners"
that clean ("trim") unused RAM every one minute.
The program is ReduceMemory by Sordum.org version 1.6.0.0.
Do You think this could cause
either the error message from above, or even the XY crashes ?
I have not had any noticeable problems
with any other program since using ReduceMemory.
Off course, disabling/closing this RAM cleaner if so easy to do for me
and I will do it regardless of Your feed-back,
but it will take me two days to reliably know if
this makes any difference.

In general, I get the impression that you use a lot of wild stuff on your system which could explain any type of weird instability. RAM cleaner??? Come on!

Fair thought.

But actually, I am quite a "minimalist",
no shell extensions (other than some Windows default ones),
minimal stuff running in background,
most of my programs are portable rather than installed, etc,
all with the desire to have a faster and more stable system.
And so it is (very fast + stable), except for this XY problem I have.

As far as the RAM cleaner goes,
I did not have to wait long for feed-back :
XY just crashed a few minutes after I closed the RAM cleaner.
So that it not it.

You might be right that some item might be acting weird,
but I can assure You that I am running a minimalist system otherwise.
I believe that there is nothing else that I CAN disable.
This RAM cleaner was the only little extra "luxury" I had.
And I won't be using it any longer, I am aware of the arguments.

Still you seem to be about the only one getting those crashes at the moment. (The other two disappeared.)

Well, I can't argue with that.

Sorry for using up Your time.

I will just keep an eye on XY developments,
and will keep checking out those odd little ideas
like the once suggested earlier by Marcus etc.

Thanks !!

stoik wrote: ↑15 Sep 2024 13:53 Well, I can't argue with that.

Sorry for using up Your time.

I will just keep an eye on XY developments,
and will keep checking out those odd little ideas
like the once suggested earlier by Marcus etc.

Thanks !!

I stand still on my suggestion, which is not an "odd little idea" but the first step to try in such cases.

Quite right, Marco,
I did not mean to belittle Your idea,
by "little" I meant "simple and easy to do"
not "little" in terms of importance or intellectual quality .
And "odd" was not referring to You
but to Windows Defender mis-percieving new folder creation
as "malicious activity".

At first I thought of perhaps finding a way to
add new folder creation to Windows Defender exceptions
(no clue how to do that - seems impossible)
but then - it's not just creating new folders that crashes XY,
it is also moving files, or simply selecting the other pane
without creating anything new or moving anything.

Well, I definitely have the "disable Windows Defender"
(while unplugging from the internet for possibly 2 days - ouch !)
on my to do list, it's just such a daunting prospect (no emails for 2 days),
that is why I did not do it yet.
I will post the feed-back here (once I have it).

Thank You.

I wouldn't rule out that ram cleaner so quick either, if it crashed after you closed it, it could have already created conditions that persisted. The app looks like it takes process exclusions so you could even try keep it running, and just temporarily create a XYplorer.exe exclusion, I would recommend then restart XY after making the exclusion too.

Earlier you mentioned you lose settings after crash, not sure if you are aware, but you may be interested in this config.

Configuration | General | Startup & Exit | Save Settings | Save changes to disk immediately

Thank You, Jupe !

After I closed the RAM cleaner and restarted Windows
I was quite encouraged for a while
but just right now, close to 24 hours later,
I had a XY crash.

I am familiar with XY's setting "Save changes to disk immediately"
it is ON for years now, so I did not loose core settings for a long time now,
the only thing I do loose it the current address location,
which is not a big deal - I just navigate back to where I was.

This was not a waste of time for me personally,
I learned that I do not need that RAM cleaner after all,
with Windows 10 that is not an issue any longer.

This is my plan now : one by one
I will disable anything running in the background
which is not much, but there are still a few items
like my PDF printer service ("Doro")
and I will see what happens.
I will let You know.

stoik wrote: ↑16 Sep 2024 18:01 I am familiar with XY's setting "Save changes to disk immediately"
it is ON for years now, so I did not loose core settings for a long time now,
the only thing I do loose it the current address location,
which is not a big deal - I just navigate back to where I was.

Hmm that's not what you said earlier:

stoik wrote: ↑11 Sep 2024 17:45 If I previously made any changes to XYplorer's settings
(e.g. changed some toolbar buttons,
or changed something in XYplorer's Configuration)
these changes are not saved with this "crash"

Anyway, the plan you mentioned sounds good, doubtful about Doro being involved though.

Thanks for Your reply, Jupe.

As for "changes are not saved with this crash",
I was listing the full spectrum of the effects
that have occurred over time ...
that is not to say that they all occur all the time
and with equal 100 % frequency.

By far the most crashes (95 %) occur when creating a folder
and I loose just the last used path/address,
all the other undesired scenarios are rare but have occurred,
I was listing even the rarer scenarios - just in case
they may help You guys recognize some "symptoms of the disease".

As for Doro PDF printer, I totally agree that
is is much less likely the problem,
that is why I am only now
trying out these remaining unlikely options.

It looks like I might have solved this !

In the last 3 days I have had only 1 crash (on 3 days)
instead of the usual 6 or so (sometimes more).

What did I change 3 days ago ?
I stopped using the RAM cleaner.
When Admin was scoffing at these cleaners
higher up in this post - he (or she) was right !

I will give it a few more days before declaring total victory,
then - if this still holds - I will change the title of this post
by adding "- SOLVED".

For me this was very useful.
For Admin maybe this adds to
how to respond to complaints about crashes on this forum.
Not only should shells be disabled but also any RAM cleaners.

Thank You all for Your great ideas !

But, "only 1 crash" is also 1 too much.