Resynthesizer v1.0 released

Please no brickbats, I am using Windows 7, and I understand that GIMP 2.8 uses a new version of python, like 2.7? and Resynthesizer uses python 2.6? So does Resynthesizer work in GIMP 2.8? If so, how should I make it work?

Downloaded the tar.gz from the link, unpacked it and put everything in ~/.gimp-2.7/plug-ins. Start gimp-2.7, load an image, make a small selection, then Filters>Enhance>Heal Selection. Choosing it brings up a small gui with boxes for Context sampling, Sample from and filling order. Selecting OK brings up the following error messages:
eoor: procedure not found
More information:
Traceback (most recent call last):
File "/opt/gimp/lib/gimp/2.0/python/gimpfu.py", line 699, in response
dialog.res = run_script(params)
File "/opt/gimp/lib/gimp/2.0/python/gimpfu.py", line 361, in run_script
return apply(function, params)
File "/home/greenman/.gimp-2.7/plug-ins/plugin-heal-selection.py", line 148, in heal_selection
pdb.plug_in_resynthesizer(timg, tdrawable, 0,0, useBorder, work_drawable.ID, -1, -1, 0.0, 0.117, 16, 500)
error: procedure not found

and

Calling error for procedure 'gimp-procedural-db-proc-info':
Procedure 'plug-in-resynthesizer' not found

Clicking cancel brings up the following:
WARNING: Plug-In "plugin-heal-selection.py"
(/home/greenman/.gimp-2.7/plug-ins/plugin-heal-selection.py)
called deprecated procedure 'gimp-selection-combine'.
It should call 'gimp-image-select-item' instead!

This is starting with a "clean" gimp-2.7 installation, ~/.gimp-2.6 renamed before starting gimp-2.7, so no old plugins copied over.

Please somebody take time to look into memory usage / allocations, etc.

I noticed that in 'resynth-map-types.h' there are two 'g_malloc' instructions, one of them taking a 'guint' as a parameter and the other one taking a 'gint'. That is limiting the maximum memory allocation to 4GiB and 2GiB respectively. That's just too low for some huge images.
Please change the parameter type to 'gsize' so us 64-bit users can allocate ~18 Exabytes. :)

Also I noticed that with an image roughly 7500x7500, with a selection taking almost the whole image, and using the command 'Heal selection', in 'resynthesizer.c', line 651 (function prepare_sorted_offsets(), instruction g_array_sized_new), it tries to allocate 1809372168 bytes (~1.8GiB) which I don't have at the moment of executing the script (roughly 1.1GiB free, almost all of them from swap).
My system has 2GiB RAM + 2GiB swap, and I'm trying to fill a black section of an image which is the result of a panorama stitch. The stitching process leaves black areas for zones without data, such as the nadir (the ground). The resulting images are usually huge in size (e.g. 20k * 10k), but they can be broken into 6 cube faces for easier processing. The problem is that the ground face usually contains large black areas (unless you shoot absolutely everything 360ºx180º).
I mentioned that cause it's an interesting use case.
With the current memory usage of this plugin these things become almost impossible to do in memory limited systems.

Please look into any memory optimization you could think of.
RAM may be cheap, but free RAM slots are not. ;)