Upgrading 2sxc from 11.02 to 11.07.02 the site runs very slow because of ImageResizer DLL

I’m submitting a bug report or not sure.

About Upgrading or other / unknown.

Current behavior I started with a fast/small site running DNN 8.00.04, with 2sxc 11.02 installed and working. The only 2 other modules are DNN Sharp’s ActionForm (old version, 3.7.3) and EasyDNN News 7.6.0.

I made a backup, installed 2sxc 11.07.02 (latest) and the install appear successful, however, each page-load took 90 to 120 seconds. After more testing and not finding many errors logged, I restored the site and tried again.

I started again with 2sxc 11.02 and upgraded to just v11.03, same exact results.

Should 2sxc 11.03 and higher still be compatible with DNN 8.00.04?

Expected behavior Upgrade 2sxc to latest and everything work AND run at normal speed.

Minimal reproduction of the problem with instructions Not sure, but if you have a DNN 8.00.04 site with same module, try it? 😉

Please tell us about your environment: Win Server 2016, SQL 2016, etc

2sxc version(s): 11.02 upgrading to 11.03 or 11.07.02 Browser all DNN 8.00.04

I can successfully load each page on the site by waiting 2 minutes and no errors get logged.

Here are the only 2 error messages I can find after the update. I am not even sure it is related?

2020-10-03 11:39:30,045 [H2036v06][Thread:40][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.Exception: File load failed, aborting
2020-10-03 11:50:28,205 [H2036v06][Thread:50][ERROR] DotNetNuke.Services.Exceptions.Exceptions - System.IO.IOException: The process cannot access the file '... \web\DesktopModules\ToSIC_SexyContent\Upgrade\Log\2020-10-03 16-50-28-2053899-5524-5.log.resources' because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at ToSic.Sxc.Dnn.Install.DnnInstallLogger.OpenLogFiles() in C:\Projects\2sxc\2sxc\Src\Dnn\ToSic.Sxc.Dnn\Dnn\Install\DnnInstallLogger.cs:line 43
   at ToSic.Sxc.Dnn.Install.InstallationController.IsUpgradeComplete(String version, String note) in C:\Projects\2sxc\2sxc\Src\Dnn\ToSic.Sxc.Dnn\Dnn\Install\InstallationController_IsRunning.cs:line 10
   at ToSic.Sxc.Dnn.Install.InstallationController.UpdateUpgradeCompleteStatus() in C:\Projects\2sxc\2sxc\Src\Dnn\ToSic.Sxc.Dnn\Dnn\Install\InstallationController_Statics.cs:line 14
   at ToSic.Sxc.Dnn.Install.InstallationController.UpgradeModule(String version) in C:\Projects\2sxc\2sxc\Src\Dnn\ToSic.Sxc.Dnn\Dnn\Install\InstallationController.cs:line 139
   at ToSic.SexyContent.Environment.Dnn7.DnnBusinessController.UpgradeModule(String version) in C:\Projects\2sxc\2sxc\Src\Dnn\ToSic.Sxc.Dnn\Environment\Dnn7\DnnBusinessController.cs:line 89
   at DotNetNuke.Entities.Modules.EventMessageProcessor.UpgradeModule(EventMessage message)

[MS-BSI]

Yes, that was my debugging method (+ DLL deletion) since 1 hour (because of the slowness).

I found the culprit line of code : <add name="ImageResizingModule" type="ImageResizer.InterceptModule" />

When commented, all is back to the normal 😉

[iJungleboy]

@MS-BSI Awesome - thanks for the update!!!

I have a vague idea of how that could be. Could you test it?

In one of the later version of 2sxc we upgraded image resizer and added WebP support

  <resizer>
    <pipeline defaultCommands="autorotate.default=true" />
    <plugins>
      <add name="DiskCache" />
      <add name="WebPEncoder" downloadnativedependencies="true" /> <!-- this line -->
    </plugins>
  </resizer>

The mechanism is a bit strange, but it basically will (try to) add another DLL from google to do WebP conversion, and I could imagine that this somehow fails. Maybe the server can’t access the internet or whatever - but I’m just guessing.

Could you try to reactivate the image-resizer-module and deactivate the WebP, and if that works, reactivate webP but disable downloadnative... ?