Ads were blocked by your webbrowser.

This is not a problem, but keep in mind that developing HeidiSQL, user support and hosting takes time and money.

You may want to send a donation instead.

Heidi maxes out RAM when closing

aSystemOverload's profile image aSystemOverload posted 5 months ago in General

Hey, twice now, after updating to 10.1.0.5546 (64bit), I've attempted to close Heidi, whilst there were 4 or 5 query tabs open, some saved, some not. It doesn't close and becomes unresponsive, checking Task Manager, it is using 10 Gb of RAM (I've got 16) and my laptop is overheating, the fans going crazy. Both times I've had to END-TASK the process.

Any idea what is going on?

Win10.

ansgar's profile image ansgar posted 5 months ago

Probably also caused by the bug which is causing issue #620.

aSystemOverload's profile image aSystemOverload posted 5 months ago

I was exporting large datasets prior to this happening.



Ads were blocked by your webbrowser.

This is not a problem, but keep in mind that developing HeidiSQL, user support and hosting takes time and money.

You may want to send a donation instead.
aSystemOverload's profile image aSystemOverload posted 4 months ago

Has the bug been resolved? I can confirm, that as of v10.1.0.5559 (64bit), I am still experiencing it. I powered my laptop back up after putting it into SLEEP, but other priorities kept me from getting on with work, one hour later, it has reached 5.2 GB RAM. I tru to interact with it and I get [an error occurred]. Bug Report attached. This could be the same as the other I posted earlier today, how soon it 'crashes' could depend on whether you attempt to interact with it.

1 attachment(s):
ansgar's profile image ansgar posted 4 months ago

Yes, I fixed issue #620 . But that did not seem to be the cause for your issue. Instead, I saw exactly the same crash in .BindParamsActivated from another user. He reported that HeidiSQL's window was invisible somehow. Maybe you had a similar issue? I also did not yet get feedback for the regedit workaround I posted there.

aSystemOverload's profile image aSystemOverload posted 4 months ago

Just to confirm, this (resuming machine where Heidi was present on SLEEP results in steadily increasing RAM and no ability to interact with GUI) is still an issue with v10.1.0.5562.

aSystemOverload's profile image aSystemOverload posted 3 months ago

Still an issue with 10.1.0.5585. Just resumed and heidi is non-responsive and using 50 - 60% CPU, RAM currently at 2.6GB and climbing. Had to end-task as I needed to use it, there were no crash screens.

Windows Logs provide these two logs:

The program heidisql.exe version 10.1.0.5585 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 468 Start Time: 01d51af88351fb67 Termination Time: 4294967295 Application Path: C:\Program Files\HeidiSQL\heidisql.exe Report Id: 070193f4-62bf-4a83-85ed-3a45536900ad Faulting package full name: Faulting package-relative application ID:

Fault bucket 1413226069085520128, type 5 Event Name: AppHangB1 Response: Not available Cab Id: 0

Problem signature: P1: heidisql.exe P2: 10.1.0.5585 P3: 5cf573a1 P4: 4aa5 P5: 67246080 P6: P7: P8: P9: P10:

Attached files: \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1166.tmp.WERInternalMetadata.xml

These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_heidisql.exe_c47e29459b553b633d45635af41650a3b9ea67e7_32b228e4_04f014c2

Analysis symbol: Rechecking for solution: 0 Report Id: 070193f4-62bf-4a83-85ed-3a45536900ad Report Status: 268435456 Hashed bucket: 340b8d3c5244d238c39cc99f4b2a0100 Cab Guid: 0

aSystemOverload's profile image aSystemOverload posted 3 months ago

Any luck on identifying the issue, currently on 10.2.0.5599

1 attachment(s):
  • Heidi_MaxRamissue_2019-06-21

Please login to leave a reply, or register at first.