Update all lists at once "crashing" on last two version so far?

[StormJumper]

I noticed lately since 121 and now 122 version of FMD that anytime I do the option "Update all lists at once" that while checking it will crash and case a debug error. I didn't change anything from before the previous list and it updated without problems. Is this something related to the sites or how it check with the manga sites? Including my debug file for checkup as since it is something different from before and I can't open to see what and where the error occurred. So if you could look at my debug file and tell me what happened and where. This is for version fmd_0.9.122.0_Win64.

fmd.zip

[riderkick]

You should post your fmd.log, not dbg file. Dbg file is just a library for app to locate information of compiled unit for debugging purposes.

[StormJumper]

oh ok...I'll try looking for that again. I don't recall that it created that file when it crashed - when I did the "Update all list at once" but I will try it again to see if the fmd.log shows up or if I missed it. Here's what I found if I check the box to create fmd.log - FMD freezes and does nothing. This is what happens every-time I enable this option. In the past FMD it auto created the fmd.log but now if the option is checked it freezes. So now what?

[riderkick]

Try to change the log file location. Or create that file first with empty content. Make sure the permission is correct. Also check your antivirus/defenders or other program that may interfere. Also try to change the location of your fmd installation. The method for creating the log file is the same as others file like config.ini, downloads.db etc. So if fmd can create those file its should be able to create the log file. Except when something interfere.

[StormJumper]

I had no other problems when I unzip and move and copied the favorites to the new folder had no issue running them. Here is a screen shot of the problem. FMD favorite check error.zip

[riderkick]

You obviously had permission issue. That line pointed out it can't write the log file. I'm aware there is some antivirus/defender that block access to the file permanently. Or there is corrupt permission with that path. Try to change the log filename to something else. works\mylog.txt for example.

[riderkick]

Try this. It will show an error message if failed to write to log file. Disable/enable the log in settings to push the error message. fmd_0.9.123.0.7z.txt

[StormJumper]

So it can't write the log but I don't recall this issue from previous FMD in Windows 7 and in Windows 10 the problem didn't appear til later. But it's unzip onto a separate HDD that run FMD why would that cause the log problem when using it? I had this same setup before and when a error happened it created a log file. But the A/V is Defender and I had MSE with Windows 7 both are Microsoft products of the same program. So how do I view that file?

[riderkick]

Can you write the log with another filename? What it show about failed to write file? Access denied or something else. There is many thing that can cause the problem. Permission issue (read only flag etc), antivirus/defender, corrupt file, corrupt disk. You need to find more information about your situation. Look for event viewer for example.

[StormJumper]

The folder for FMD itself is on a separate HDD so I woudn't think permission was a problem here when it wrote to the fdm.log file itself? I know in the past previous FMD before this problem showed up would write a fmd.log file and I could open and read it. But lately with the update and changes if I select it to create a log file with different name even with *.log it would freeze fdm itself til I killed the program and went to the config.ini and changed it from 1 to 0 and then would I be able to run fmd again. Also before I let it sit there when I did that before to create the log file and it did nothing nor did it give a error report back and I had to terminate the program and change the config.ini to be able to run fmd again.

[riderkick]

Do you even try the latest version? It has check for io result. It will show the io result instead of throwing another exception which causing to enter infinite loop. Which appear to be freeze but it's not internally.

What the io result you got?

[riderkick]

I feel like talking to a wall here. I'm asking what the result with different path/filename. Whatever you like. log.txt, fmd.log, downloads.db, mylog.csv, errorlog. Anything. Even appending to possible accessible file. Like config\config.ini If its failed to write to those file it will show the information in log window. What the error message ? Simply answer that. You are not being productive at all.

[StormJumper]

I tried to create a log file on the E: drive but when I click apply FMD just freezes and does nothing until I kill the program. If it created a error file I would see it but there is nothing there. I don't get any error windows that is why I only got the error screen shot I was able to capture is all nothing more. I though I would get a error log or file but got nothing. I'll try to create the log file on a different HDD not on C: and see what happens but if it just freezes fmd when I apply the option then there is no error for me to post.

[riderkick]

Like I said, the freeze is because its trapped in exception loop. When there is an exception(error), its try to write to file the messages, but failed. So, its create another exception for it, but failed and create another exception for that failed attempt. And so on trapped in loop. This commit should fix that https://github.com/riderkick/FMD/commit/f59d81836a9e2882db44b1e303f3b85df918f63f , which is shipped in 0.9.124.0.

You keep repeating the same thing. We are on loop here. On unproductive conversation. It seems you don't even do what I asked with your words and see what happens. Just answer when you already done what I asked! You are not cooperative at all.

Here is what you have to do, only reply when you already do it.

• Download the latest version.
• Unpack it to a new location.
• Open log window, Options > Misc > Open Log.
• Change the log file location to log.txt.
• Thick Stay on top checkbox (optional).
• Back to main windows and thick Enable logging. Click apply.
• Post the log message with screenshot.

Here is my log when I flag the file with read only.

And here is the log when I use an invalid location .

[StormJumper]

ok, I'll try that this week. So what do I do if the revised version works how do I transfer my favorites without loosing it?