Constant debugging error

[kaihao]

Hi Hector,

I recently got a new desktop and unfortunately have been having a lot of issues with Coollector.
It does not seem to matter what I was doing (scanning folder to add new movie, filtering, adjusting style, or even simply scrolling through my movies, etc), I constantly getting the same debugging errors (see attached screenshot for error message). After the program shut down, it automatically opened up a folder with couple files inside (coollector.dmp and coollector.xml). Both are also attached.

By the way, this happened on my old PC also but it was a few and far between.
I hope there is a solution to this because I love Coollector and would want to continue using it.

Thanks!!

Kai

Attachments

Coollector.xml

(7.41 KiB) Downloaded 232 times

Coollector.dmp

(222.15 KiB) Downloaded 258 times

[(cool) Hector]

Thank you for reporting your problems!

Are you using a skin or are you using the default one?

[(cool) Hector]

The text on your screenshot is very big. What's the resolution of your screen? Is it High DPI or are you visually disabled?

I ask all this because the program doesn't crash for me and I try to understand why it crashes for you...

[kaihao]

Default skin.
This is a HTPC so I am using TV as the display.
Resolution is 3840x2160 (Recommended) and scale is 300% (Recommended).
I changed scale to 100% and immediately got the debug error so you may be onto something.
The fonts look tiny though when I do that so I would need to stick to 300%.

Please let me know if you need more info.

Thanks,
Kai

[(cool) Hector]

Are you in single-pane mode or in dual-pane mode?

It's just a hunch but my guess is that you're in single-pane mode and it'll stop crashing if you go into dual-pane mode. Right or wrong?

[(cool) Hector]

After the program shut down, it automatically opened up a folder with couple files inside (coollector.dmp and coollector.xml).

It's great that the crash creates a crash dump, but unfortunately the crash dump created by the release version of the app doesn't contain enough information.

Here's a link to the debug version:

https://www.coollector.com/Coollector.DEBUG.exe

If you run it and succeed to make it crash, then give me the 2 files of the crash dump and I should be able to analyze the crash.

Thank you very much for helping me fix this bug!

[kaihao]

You're right about the single-pane.
It has not crashed since I switched to dual-pane.
I still prefer single-pane though if it is fixable.

Attached are the 2 files that I got from the debug.exe file.

Attachments

Coollector.xml

(10.63 KiB) Downloaded 250 times

Coollector.dmp

(187.22 KiB) Downloaded 246 times

[(cool) Hector]

You're a champ! The dump looks great, I look into it later today.

[(cool) Hector]

This is a HTPC

Is it an old PC? How much RAM does it have? Are you sure it's not a little under-specced to handle such big graphics?

I ask because it's weird where the app crashes... The app creates a 2985x1648 bitmap where it'll draw the grid's content but the bitmap ends up being invalid...

If your PC has only 4GB of RAM, it's not enough to run Windows nowadays. My mom's computer had only 4GB of RAM, worked fine for a long time, but a few years ago the web browser started crashing constantly. Upgraded to 8GB of RAM and the problem was solved.

[(cool) Hector]

It has not crashed since I switched to dual-pane.
I still prefer single-pane though if it is fixable.

Looks like it works in dual-pane mode because the graphics are twice smaller.

Do you confirm that you only have 4GB of RAM? If that's indeed the case, it could be wise to upgrade your RAM

[kaihao]

Nope, it's a brand new PC and has a 12MB RAM.
It only has onboard graphic card though if that matters.

[(cool) Hector]

Ok, I will look further...

[kaihao]

Ok thanks and good luck!

[(cool) Hector]

I'm afraid I'm running out of ideas, the only thing that I can think of is a RAM issue.

it's a brand new PC and has a 12MB RAM.

Do you confirm that the 12MB are well detected by the system?

https://www.tenforums.com/attachments/tutorials/105828d1476388173-determine-system-memory-size-speed-type-windows-10-a-memory_size_settings.png

Did your brand new PC come with 12MB installed? or was it just 4MB and you added 8MB yourself?

Sometimes a RAM module doesn't work well with another RAM module, I've already had the case and the result was that one of the modules died shortly after.

Is it possible to make a test with only the 8MB module?

[kaihao]

It came with 12MB installed and I have confirmed all 12MB are recognized by the system.