Meshlab crashes everytime it's opned about meshlab

[gibbycu]

I had the same error. The solution for me was to right click on my desktop, go to NVIDIA Control Panel, go to Manage 3D Settings, then under preferred graphics processor choose your preferred processor. All fired up after that. Something about the auto-select was causing problems.

[eboudrand]

@granzuglia I did not format only because of Meshlab. I had also problems with my bluetooth device ;).

I suspect the issue is due to migration to Windows 10. My computer's manufacturer warned :

Product not tested for Windows 10 upgrade. If you choose to upgrade, some features, applications, and connected devices may not work as expected.

I found another solution there :

By starting the program by "right click / Execute with the graphics processor / Nvidia" instead of "Intel (default)" the problem disappeared.

[ChrisB1985]

Snap. It loads the gui which is progress on the previous version but then crashes out with a dialog stating "meshlab.exe has stopped working"

[michaelneiss]

After a few months of failed attempts, I finally found a solution that made MeshLab 2016 run! On my HP Pavilion dv6-6130eo, the problem was solved by setting the switchable graphics in the BIOS to "fixed mode" as described here:
https://support.hp.com/us-en/document/c02948560?jumpid=reg_r1002_usen_c-001_title_r0001
Good luck!

[mbouksim]

Forget to mention my OS
windows 7 ultimate 64 bits
Core i5-2450M 2.50GHz and 4Go of Ram
it happen also on windows server 2012 r2 64 bits

[granzuglia]

Can you try to install the package contained at this link https://support.microsoft.com/en-us/kb/2999226 being careful to select the version related with your specific version of the Windows OS? It looks like it could be an issue related with a not updated version of the file ucrtbase.dll. It's difficult for us to replicate the problem so we can just try to guess which could be the solution. Sorry for the inconvenience but probably (and i highlight "probably") it's independent from MeshLab itself.

[mbouksim]

Thank you for your help but I already tried it (Sorry forgot to mention it on the first post), but still the same problem.
I tied it on Core i7 and 6Go of Ram with dual GPU on windows 10 64 bits and got the same problem
could it be a compatibility problem with the dual GPU?

[granzuglia]

Can you try to launch meshlabserver.exe (it is included in the same directory where meshlab.exe is installed)? do you get the same crash or do you get the info on how to use meshlabserver?

[mbouksim]

when I launch meshlabserver.exe I get the info on how to use it , and when I execute any command with the server I get the following errors

Failed to load libEGL (The specified module could not be found.)
QWindowsEGLStaticContext::create: Failed to load and resolve libEGL functions
Failed to load opengl32sw.dll (The specified module could not be found.)
Failed to load and resolve WGL/OpenGL functions
Failed to load libEGL (The specified module could not be found.)
QWindowsEGLStaticContext::create: Failed to load and resolve libEGL functions
Failed to load opengl32sw.dll (The specified module could not be found.)
Failed to load and resolve WGL/OpenGL functions
GLEW Init: failed!

[karhid]

same issue for me too running on windows 10 64 bits
core i5 and 6 GB of ram and I have also dual GPU Nvidia and Intel

[mbouksim]

Thank you @gibbycu for your answer but it didn't work for me tried with both GPU but still got the same problem :/

[ChrisB1985]

I have found the same issue.
Windows 10 pro x64, Intel i3-2370M, 8GB RAM, Intel HD graphics 3000 (just the one display adaptor).
It's an old laptop with a recent windows 10 installation (couple of weeks) and as such does not have much other software installed.
Event viewer points me toward ucrtbase.dll similar to the above. My ucrtbase.dll version is 10.0.14393.0

If I can provide any logs etc which may help in resolving this please let me know

[eboudrand]

I have the same issue. I can install and run Meshlab 1.3.4 BETA but not Meshlab 2016. So, there must have been a change somewhere in Meshlab code. The lack of logs in the application is helpless for finding the cause of the issue.

I have recompiled the application and I cannot get it starting. It stops in MLSceneGLSharedDataContext::initializeGL() by executing throw MLException("MLSceneGLSharedDataContext: GLEW initialization failed\n"). glewContextInit() is returning GLEW_ERROR_NO_GL_VERSION because glGetString(GL_VERSION) is returning 0. When I read report from @mbouksim, I suspect a problem with OpenGL.

If Meshlab 1.3.4 is already installed, I can run Meshlab 2016 but I have errors. I cannot use it.

[granzuglia]

thanks a lot for the report! We are not able to replicate it, even if we tried with tens of laptops and pc, but now at least we can try to focus in something more specific!

[eboudrand]

I think some logs should be working from the beginning the application is launched. From what I read in the code, logs are only generated for been displayed in a TextEdit widget.

[granzuglia]

Can you try to launch a simple processing on MeshLabServer? MeshLabServer invokes also the glewInit function. It would be useful to know if it fails there too or not. Thanks!

[eboudrand]

meslabserver failed also. glewInit() returned GLEW_ERROR_NO_GL_VERSION in main function.

[granzuglia]

Hmmmm! can you give me all the possible specifications of your graphics card, including the driver version you have installed? Thanks again for your help!

[eboudrand]

I am using a graphic card based on Mobile Intel 4 Series Express Chipset Family. Driver version is 8.15.10.2702.

[mbouksim]

@eboudrand I thought the same thing, tried to make a clean installation of My GPU driver and update them to the last version but still got the same error
here is my GPU information if it could help

[ChrisB1985]

I'm seeing a common trend here...

[granzuglia]

Ok. It looks like we could have troubles with the Intel Integrated graphics cards. I have one too on my laptop along with a more performing Nvidia GPU and it doesn't seem to cause problems. Do you have just this card on your laptop? We will try to find a pc with only an integrated graphics card on it or with the most similar possible integrated graphics card to the one you have and try to replicate the issue. Thanks a lot for your collaborations. If you find some other info that you can think it may help us to resolve the problem, please, feel free to publish it here. We want to provide you the best software possible or at least, allow you to run it :D

[ChrisB1985]

Well thank you very much for the support. My laptop only has the one graphics card... it's a fairly cheap one! I may not be a great help with debugging but I can certainly test any updated/patched versions.

[granzuglia]

Dear guys, we need your help. can you try to install and launch this version of MeshLab? vcg.isti.cnr.it/~ranzuglia/MeshLab2016.12_2017_01_17.exe
Probably it will not work anyway but being unable to reproduce the crash in any of the laptops/pc's we installed MeshLab the only way that we have to try to fix your problem it is trying to guess a possible solution, arrange an on-the-fly release and ask you to kindly test it for us. This process probably will take quite a long time. Ignore for the moment MeshLabServer. Please, consider that the VCLab-ISTI-CNR is not rich at all and we take major efforts to maintain MeshLab opensource and free to be downloaded.

[granzuglia]

Please, report it even if it doesn't work :)

[ChrisB1985]

Thanks for that, I'll have a look after work today.
I do remember having problems with Intel graphics cards and repetier host on Windows 10 which were caused by open gl. It may be entirely unrelated but there was a thread on their forum which eventually found a solution...
http://forum.repetier.com/discussion/972/random-crashes-after-upgrade-to-windows-10-and-latest-1-5

[eboudrand]

It still crash, but not in the same function. I can see the UI.

I started meshlab.exe from WinDbg and it outputs :

0:000> g
(269c.21c0): Unknown exception - code c000041d (!!! second chance !!!)
Qt5Gui!QOpenGLContext::functions+0x6:
00007ff9d6b72856 488b5908 mov rbx,qword ptr [rcx+8] ds:0000000000000008=????????????????

Here is the stack :

0:000> kb
 # RetAddr           : Args to Child                                                           : Call Site
00 00000000`639006b1 : 000001e8`5e4a5110 00000000`643613d7 00000000`00000005 00000000`6390097f : Qt5Gui!QOpenGLContext::functions+0x6
01 00000000`6390b3af : 000001e8`5e4a5110 000001e8`5d5ac090 000001e8`5e492e28 00000000`63911372 : Qt5OpenGL!QGLWidgetGLPaintDevice::beginPaint+0x21
02 00007ff9`d6d02fd9 : 00000294`00000500 00007ff9`d6e619b8 000001e8`5e332370 000001e8`5e332370 : Qt5OpenGL!QGL2PaintEngineEx::begin+0x18f
03 00007ff9`d6d01fda : 000000a6`350fa470 00000000`00000004 000001e8`5e332370 00000000`00000000 : Qt5Gui!QPainter::begin+0x3c9
04 00007ff7`2af05f81 : 000001e8`5e332360 00000000`64340000 00000000`00000004 00000000`00000004 : Qt5Gui!QPainter::QPainter+0x6a
05 00000000`64381385 : 000001e8`5a580000 00000000`64340000 000001e8`5e332360 000001e8`5e332360 : image00007ff7_2aed0000+0x35f81
06 00000000`643578f0 : 000001e8`5a593ef0 000001e8`5e332360 000001e8`5e332360 000000a6`350fb230 : Qt5Widgets!QWidget::event+0x5a5
07 00000000`64356822 : 000001e8`5a5d7d30 000000a6`350faa60 000000a6`350fb230 000001e8`5a580000 : Qt5Widgets!QApplicationPrivate::notify_helper+0x140
08 00007ff7`2afd79e3 : 000000a6`350ff770 000001e8`5a5d7d30 000000a6`350fb230 00000293`00000400 : Qt5Widgets!QApplication::notify+0x1b72
09 00000000`63b4d309 : 000001e8`5e332360 000000a6`350fb230 3ff00000`00000000 000001e8`5e332360 : image00007ff7_2aed0000+0x1079e3
0a 00000000`64380903 : 000001e8`5e332360 00007ff9`d6e619b8 000001e8`5e332360 00000000`639a7126 : Qt5Core!QCoreApplication::notifyInternal2+0xb9
0b 00000000`64360d86 : ffffffc5`00000000 000001e8`5e332d80 00000000`00000000 00000000`64395bf1 : Qt5Widgets!QWidgetPrivate::drawWidget+0x8b3
0c 00000000`643a6d70 : 000001e8`5dc589b0 000001e8`5e332d80 00000000`00000000 000000a6`350fbc60 : Qt5Widgets!QWidgetPrivate::repaint_sys+0x236
0d 00000000`643578f0 : 000001e8`5e332d80 000001e8`5a593ef0 000001e8`5e332d80 000000a6`350fbc60 : Qt5Widgets!QSizePolicy::QSizePolicy+0xb70
0e 00000000`64356822 : 000001e8`5a593ef0 000000a6`350fb500 000000a6`350fbc60 000001e8`5a593ef0 : Qt5Widgets!QApplicationPrivate::notify_helper+0x140
0f 00007ff7`2afd79e3 : 000000a6`350ff770 000001e8`5a5d7d30 000000a6`350fbc60 00000000`00000000 : Qt5Widgets!QApplication::notify+0x1b72
10 00000000`63b4d309 : 000001e8`5e46b390 000000a6`350fbc60 000001e8`5a580000 000001e8`5e332d80 : image00007ff7_2aed0000+0x1079e3
11 00007ff9`d6b404b3 : 000001e8`5e46b390 00007ffa`03680000 000001e8`5e46b390 00007ff9`d6d40b2b : Qt5Core!QCoreApplication::notifyInternal2+0xb9
12 00007ff9`d6b276bb : 00007ff9`d7066aa0 000001e8`5a593ef0 00000000`00000000 00000000`00000000 : Qt5Gui!QGuiApplicationPrivate::processExposeEvent+0x133
13 00007ff9`d6b23c32 : 000000a6`00000000 00007ff9`d7066aa0 000001e8`5a593ef0 00007ff9`d6b24d2d : Qt5Gui!QWindowSystemInterface::sendWindowSystemEvents+0x9b
14 00007ff9`d8187c37 : 000000a6`00000000 00007ff9`d7066aa0 000001e8`5e33ec60 00000000`639c4445 : Qt5Gui!QWindowSystemInterface::flushWindowSystemEvents+0x152
15 00007ff9`d819231d : ffffffff`00000000 00000000`00010001 00000000`00010001 000001e8`5e33ec60 : qwindows+0x7c37
16 00007ff9`d819294b : 00000000`0000000f 0000269c`0000269c 00000000`0000000f 00000000`00000000 : qwindows+0x1231d
17 00007ffa`03e91c24 : 00000000`00030a78 00000000`00000001 00000000`00000000 00000000`00000000 : qwindows+0x1294b
18 00007ffa`03e91917 : 00000000`00000000 00007ff9`d81928f0 00000000`00030a78 00000000`00000000 : USER32!UserCallWinProcCheckWow+0x274
19 00007ffa`03ea2563 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USER32!DispatchClientMessage+0xa7
1a 00007ffa`06749c54 : 00000000`00000000 00007ffa`06749c54 00000000`00000000 00000000`00000000 : USER32!_fnDWORD+0x33
1b 00007ffa`03781764 : 00007ffa`03e915ef 00000000`0000000f 00000000`00000000 00000000`00000000 : ntdll!KiUserCallbackDispatcherContinue
1c 00007ffa`03e915ef : 00000000`0000000f 00000000`00000000 00000000`00000000 0000010e`05042063 : win32u!NtUserDispatchMessage+0x14
1d 00000000`63b92ea6 : 000000a6`350fc338 000001e8`5a5ee401 000000a6`350fc3f0 00000000`00000000 : USER32!DispatchMessageWorker+0x22f
1e 00007ff9`d81dd639 : ffffffff`fffffffe 000001e8`00000000 00000000`00000000 000001e8`5a5c5ff0 : Qt5Core!QEventDispatcherWin32::processEvents+0x546
1f 00000000`63b4d8c2 : 000001e8`5dc59480 00000000`00000000 000001e8`5a5c5ff0 000001e8`5a5d7a90 : qwindows!qt_plugin_query_metadata+0x24a9
20 00007ff7`2af19360 : 000001e8`00000000 000001e8`5dc59480 000001e8`5a5c5ff0 00000000`00000000 : Qt5Core!QCoreApplication::processEvents+0x22
21 00007ff7`2aff92f4 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffffff`ffffffff : image00007ff7_2aed0000+0x49360
22 00007ff7`2aff8503 : 00000000`0000000a 00000000`00000000 00000000`00000000 00000000`00000000 : image00007ff7_2aed0000+0x1292f4
23 00007ffa`06368364 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : image00007ff7_2aed0000+0x128503
24 00007ffa`067070d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNEL32!BaseThreadInitThunk+0x14
25 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

If you provide pdb files, it can be more precise.

[granzuglia]

Mmm...it looks like we are moving in the right way...but it's really hard to guess how to fix it without a crashing laptop :(

[mbouksim]

@granzuglia I don't know if it can help but I can provide an RDP PC having the same issue with meshlab the only problem it have a low spec. Tell me if you need it I'll send it to you

[eboudrand]

I swapped to Linux on the same computer (I have 2 OS on it) and I compiled meshlab. I could start it without problem.

[eboudrand]

I formated my hard disk and reinstall Windows 7 on my computer. After this, I could run Meshlab.2016.

[granzuglia]

I'm sorry to hear that you need a such drastic solution :( ...but as you can see from yourself the are some hints suggesting that the problem derives more from the operating system than MeshLab itself...anyway we are still trying to investigate if we are able to fix the issue.

[dylanbrams]

When I set up my graphics to prefer the NVIDIA acceleration on my Lenovo T530 I do okay until I load large files. Is there any way I can help with this?

[mcallieri]

what do you mean by "large"? if large is larger than videocard memory, or PC memory, there is nothing you can do.

[dylanbrams]

File sizes range between 230 megs and 2.5 GB. My computer has 11.8 GB available RAM, and the nVidia nvs 5400m is supposed to have 2 GB of memory. The onboard Intel HD Graphics 4000 doesn't show as having ANY memory according to the specs I see.

When I open the MeshLab included sample files they work okay, but once I scale up to the larger files (even a 1GB file) I start to have crashing issues while opening.

[mcallieri]

200-50MB should do fine, 1GB could already be at the limit of available memory, depending on the format and the kind of additional data (UV coordinates, normals, color)... anything larger, it may well be it's simply an out-of-memory problem.

But, how do you think it is EVEN POSSIBLE to load a 1TB file with 11GB of memory?

[dylanbrams]

Typo on the TB. The 1GB file is causing a crash on open. Sorry. So you think the memory size on the graphics processor could be at fault? I guess that makes sense. Wish it was a driver problem instead, TBH. I need to figure out how to load this 2GB file; probably end up needing a desktop with a heavier duty graphics card. Thank you.

What I was really hoping for was a way to diagnose the problem beyond watching the crash screen with its button. Is there a dump file or something in the system logs somewhere on Windows?

[mcallieri]

mostly, CPU memory. If the data does not fit GPU, everthing gets really really slow, and some functiuonality may not work, but it should be able to open it. If it is a main memory problem, the model will not load.

[dylanbrams]

I went through a full main memory test yesterday. It's slow for a little while, sometimes, but then it just dies. I'll try loading up a Linux kernel off a USB and see if that improves things.

[petr-sehnal]

Hi, I am experiencing same issues on both windows physical machine with low-spec GPU and virtual machine, both Windows and Linux.

It seems this error is related to compute capability of installed GPU.

Is there any chance Meshlab console conversion will be possible without appropriate GPU?

This functionality would be REALLY appreciated as this software seems to be the only one working for converting from WRML to PLY including colors (others are able to export ply mesh but unfortunately without coloring).

Thanks alot!

[llduncangithub]

I found the reason crash:
1)go to NVIDIA Control Panel, go to Manage 3D Settings, then under preferred graphics processor choose your NVIDIA processor(--MUST--).

and then run the meshlab.exe or F5 to run the program,it's OK!
2)if you choose other items in 1) in the NVIDIA Control Panel, like this:

click F5,you will got the result below:

sorry fail to provide the pic,too many to upload...

meshlab code below will throw exception:

GLenum glewContextInit (GLEW_CONTEXT_ARG_DEF_LIST)
{
const GLubyte* s;
GLuint dot;
GLint major, minor;
const GLubyte* extStart;
const GLubyte* extEnd;
/* query opengl version */
s = glGetString(GL_VERSION);

// s == null(0),will be crash later in func initializeGL()

dot = _glewStrCLen(s, '.');
if (dot == 0)
return GLEW_ERROR_NO_GL_VERSION;
...
}

void MLSceneGLSharedDataContext::initializeGL()
{
glewExperimental=GL_TRUE;

QGLContext* ctx = makeCurrentGLContext();
GLenum err = glewInit();
doneCurrentGLContext(ctx);

// err == 1,wrong!!!
if (err != GLEW_OK ) {
    throw MLException("MLSceneGLSharedDataContext: GLEW initialization failed\n");
}

}

hope to helpful, and i need to know why? thanks.

[das300hub]

I am still getting this issue on the latest build - has this been dealt with at all or work arounds ?

"Runtim Error!
Program:C:\Program Files\VCG\Meshlab.exe
This application has requested the runtime to terminate it in an unusual way.
Please conact the application's support team for more information "

TY

[granzuglia]

Thanks a lot for your post! As you can see we could not very little for this kind of crashes...I hope it could help also other users experiencing it. Thanks again!

[pierrexp2]

I have similar problem on MSI WT72 6QK workstation. Xeon E3-1505M v5, Quadro M3000M, 32GB ecc memory. Launch fast. Freezes after open any menu item. Can load file (63mb) sometimes. Freezes once loaded. Anyone with similar hardware experiencing problems?

[mickletown]

To join in, I have an Advent DT 1308 desktop with Intel graphics. Meshlab 2016 will not run, apart from flashing two boxes onto the screen and disappearing - not present in task manager. Tried the alternate 2016 install given earlier (vcg.isti.cnr.it/~ranzuglia/MeshLab2016.12_2017_01_17.exe) and that got me a step further with an opening screen that then told me windows had stopped it working. System is i52900 with 6Gb and windows 10 home. Any progress, or is the thread now closed?

[tineoh]

This worked for me:
https://support.microsoft.com/es-es/kb/2999226

[jermarti]

It sounds like most of this thread revolves around finding a repro for the issue.
I've discovered a simple one, start up a windows server 2016 VM in a cloud environment and try to process something using meshlabserver. I believe the VMs use the Microsoft Basic Render Driver.

I can understand meshlab having a display dependency on opengl, but meshlabserver not being able to run on cloud instances seems problematic.

[H-Tsubota]

I have same problem. MeshLab 2016 cannot start on a desktop machine but it can start on my another machine (both OS are windows10-64bit).

Graphic card on the failed machine is "Intel HD Graphics" (5th generation, its pretty old..). The one on fined work machine is "Intel HD Graphics 5000" (7.5th generation).

And I try to copy libegl.dll and libglesv2.dll (from Google Chrome's directory) to MeshLab 2016 directory but it does not work.

（Addition: MeshLab v1.3.3 can start on both machines.）

[mcallieri]

MeshLab, from the 2016 version, heavily relies on GPU for rendering. Older, integrated GPU like the intel do not have some of the features we are using. 5000 and 5500 series shoud work, provided the driver is recent enough. There is no plan for supporting non-accelerated GPUs.

[H-Tsubota]

Thank you for your comment.

I mistakenly believed that MeshLab can worke on older machine because it uses ANGLE version Qt. I'm happy if next version MeshLab does not crash but show messagebox like "Your machine dose not have required features" and exit normally.

Anyway, thanks to your comment, I see why MeshLab cannot start.

[nikolang]

I have the same issue. Crashes on startup.

My System:
Win10 64 bit
Geforce GTX 1060
Intel i5-7300HQ
8GB Ram

My driver versions should be up to date.

[mcallieri]

Hi.
The 1060 videocard is the same I have at home.. it should not be the problem

We only have confirmed non-starting issues with:

• older, integrated videocards (missing GPU features)
• notebook with double videocard, forcing the use of the integrated one
• DELL software for automatic backup (which interferes with QT)

[RegBurg]

My i7 laptop is now nearly 5 years old, it has the Intel integrated graphics controller and of course it has THIS problem.

My dilemma is WHICH laptop to upgrade to.
I see the Alienware has the invidia 1080 GPU with 8 gig of GPU ram, but the price is barely under $3000, maybe $2800 for open box or floor demo units.
I can scrape up the money, but if it won't run meshlab I will have spent about 2x what I otherwise would have.

Is it KNOWN that meshlab will in fact run on any/all laptops with Invidia 1060 or 1080 GPUs ?

[mickletown]

Have you considered using an older version of MeshLab that has nearly as many functions? I use 1.3.3 with no perceptible problems on a i5 processor desktop, and also on a core2 duo centrino laptop. The latest meshlab started me on the same thought trail as you, but I stuck with what I had. My computers are 8 and 10 years old respectively.I would buy second hand to get better value than brand new - there is a big difference in what you can get for your money! Steve On Sunday, 16 September 2018, 23:57, RegBurg <[email protected]> wrote: My i7 laptop is now nearly 5 years old, it has the Intel integrated graphics controller and of course it has THIS problem.My dilemma is WHICH laptop to upgrade to. I see the Alienware has the invidia 1080 GPU with 8 gig of GPU ram, but the price is barely under $3000, maybe $2800 for open box or floor demo units. I can scrape up the money, but if it won't run meshlab I will have spent about 2x what I otherwise would have.Is it KNOWN that meshlab will in fact run on any/all laptops with Invidia 1060 or 1080 GPUs ?— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread. | | Virus-free. www.avast.com |

[mickletown]

I forgot to add, both my units only have integrated Intel graphic processors - nothing else! If you are using free software and a cheap scanner, what is the point of spending megabucks on a computer system to run them? Steve On Monday, 17 September 2018, 9:46, "[email protected]" <[email protected]> wrote: Have you considered using an older version of MeshLab that has nearly as many functions? I use 1.3.3 with no perceptible problems on a i5 processor desktop, and also on a core2 duo centrino laptop. The latest meshlab started me on the same thought trail as you, but I stuck with what I had. My computers are 8 and 10 years old respectively.I would buy second hand to get better value than brand new - there is a big difference in what you can get for your money! Steve On Sunday, 16 September 2018, 23:57, RegBurg <[email protected]> wrote: My i7 laptop is now nearly 5 years old, it has the Intel integrated graphics controller and of course it has THIS problem.My dilemma is WHICH laptop to upgrade to. I see the Alienware has the invidia 1080 GPU with 8 gig of GPU ram, but the price is barely under $3000, maybe $2800 for open box or floor demo units. I can scrape up the money, but if it won't run meshlab I will have spent about 2x what I otherwise would have.Is it KNOWN that meshlab will in fact run on any/all laptops with Invidia 1060 or 1080 GPUs ?— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread. | | Virus-free. www.avast.com |

[RegBurg]

Yes, I have in fact been using an earlier version for the initial part of my learning curve.
It performs well (/well enough) for what I have done and attempted to do so far.

The suggestion to update pops up from time to time, as does the consumerism itch.
This laptop has been dropped, in fact it slid off the hood of a car at about 20 MPH, so the case is taped together, the power connector needs a rubber band to hold it in good electrical contact, etc.
So I'm on the verge of WANTING a new/newer laptop anyway and I want to NOT be locked out of being able to run latest/greatest GPU intensive programs.

I guess this is my real question;
Is the nvidia 10x0 series GPU the ONLY dependency for meshlab.latest ?

{That is poor wording; I mean;
Is NVIDIA 10x0 in fact a dependency, i.e. is the code written SPECIFICALLY for NVIDIA series cards ?
and if so, is it the ONLY dependency ?}

Side rhetorical question;
Why Oh why coudn't the latest/greatest version be backward compatible ?, i.e. just flop back to the old code if sooper-dooper GPU is not detected

[RegBurg]

Here's a thought (I'll play software developer here);

Somewhere along the line the meshlab code is linked with graphics libraries.
I would HOPE that the meshlab code is library independent, i.e. that there is a STANDARD graphics library call interface.
If that is the case it SHOULD be a fairly simple matter to link to e.g. intel graphics library and nvidia library and detect which to call at run time according to the detected (or "selected") options on the target system.

[sazamore]

Hello,

I had the same problem-- at program start two windows would blink, and the program wouldn't run. The error log also showed the ucrtbase.dll module failure.
I downloaded NVIDIA drivers for my specific GPU and now Meshlab runs fine.

[mickletown]

Does this link mean that the inbuilt intel GPU CAN be used with the latest version of meshlab then? I only ask because I can't afford a NVIDIA graphics card. Steve and Carol Harper01757611294 On ‎Monday‎, ‎15‎ ‎October‎ ‎2018‎ ‎17‎:‎09‎:‎47‎ ‎BST, Dr Z <[email protected]> wrote: Hello, I had the same problem-- at program start two windows would blink, and the program wouldn't run. The error log also showed the ucrtbase.dll module failure. I downloaded NVIDIA drivers for my specific GPU and now Meshlab runs fine. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread. | | Virus-free. www.avast.com |

[ChrisB1985]

I imagine not unfortunately. NVIDIA drivers will only support NVIDIA graphics cards. Those of us with Intel integrated graphics are still stuck. Older versions on meshlab still work apparently though if so one could provide a link. Also, best to remove your phone number from your signatures! Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: mickletown <[email protected]> Sent: Monday, October 15, 2018 5:38:43 PM To: cnr-isti-vclab/meshlab Cc: ChrisB1985; Comment Subject: Re: [cnr-isti-vclab/meshlab] Meshlab crashes everytime it's opned (#29) Does this link mean that the inbuilt intel GPU CAN be used with the latest version of meshlab then? I only ask because I can't afford a NVIDIA graphics card. Steve and Carol Harper01757611294 On ‎Monday‎, ‎15‎ ‎October‎ ‎2018‎ ‎17‎:‎09‎:‎47‎ ‎BST, Dr Z <[email protected]> wrote: Hello, I had the same problem-- at program start two windows would blink, and the program wouldn't run. The error log also showed the ucrtbase.dll module failure. I downloaded NVIDIA drivers for my specific GPU and now Meshlab runs fine. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread. | | Virus-free. www.avast.com | — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#29 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AX56_RHyhUM2-1mnwW4ha4lrsmIAQdqnks5ulLoSgaJpZM4LXQ4z>.

[RegBurg]

Agisoft (an expen$ive Commercial product, I know) solves it by detecting GPUs and providing controls over which (and perhaps how many ?) to use if more than one are detected.
On the trial version (free for 30 days) performance seems good enough for what I am currently doing and it really does look like a commercial "packaging" of the opensource tools.
As I said; expensive, so impractical for me at this time.

[wuestenarchitekten]

same issue here. tried old releases and new releases on Desktop machine, no integrated videocard...:

meshlab.exe

Summary
Stopped working

Date
‎2019-‎10-‎10 2:23 PM

Status
Report sent

Description
Faulting Application Path:	F:\Downloads\MeshLab_20190820\distrib\meshlab.exe

Problem signature
Problem Event Name:	BEX64
Application Name:	meshlab.exe
Application Version:	0.0.0.0
Application Timestamp:	5d5c3ac9
Fault Module Name:	ucrtbase.dll
Fault Module Version:	10.0.18362.387
Fault Module Timestamp:	4361b720
Exception Offset:	000000000006db8e
Exception Code:	c0000409
Exception Data:	0000000000000007
OS Version:	10.0.18362.2.0.0.256.48
Locale ID:	4105
Additional Information 1:	9741
Additional Information 2:	97414aa87c3415f3887670f67b1010d7
Additional Information 3:	d113
Additional Information 4:	d11371f86bbfc9d4bd0d6e15ee69ab3d

Extra information about the problem
Bucket ID:	c1cf0fb6c98cd6657d6ad23520f2efeb (2119737700259131371)

Windows 10 Pro, build 1903, NVIDIA Quadro P5000 latest drivers.

[alemuntoni]

Hi everybody,

I am closing this issue due to inactivity and because it refers to old MeshLab versions. Part of the problems should be resolved in the last version (2020.04).
Please try the new version and if the problem persists, feel free to open a new issue!

[mickletown]

Sorry gang, but the original fault that I reported remains even in this update! A quick couple of flashes on the screen and nothing more.I have had more success using an older version from 2016 or earlier. I know my machine is probably prehistoric compared with some that developers use, but there are very few programmes it will not support on the Windows platform. Steve On Thursday, 9 April 2020, 17:01:04 BST, Alessandro Muntoni <[email protected]> wrote: Closed #29. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[michaelneiss]

Have you tried the fix that I recommended? Regards, Michael

…

________________________________ Från: mickletown <[email protected]> Skickat: den 9 april 2020 09:51 Till: cnr-isti-vclab/meshlab <[email protected]> Kopia: michaelneiss <[email protected]>; Comment <[email protected]> Ämne: Re: [cnr-isti-vclab/meshlab] Meshlab crashes everytime it's opned (#29) Sorry gang, but the original fault that I reported remains even in this update! A quick couple of flashes on the screen and nothing more.I have had more success using an older version from 2016 or earlier. I know my machine is probably prehistoric compared with some that developers use, but there are very few programmes it will not support on the Windows platform. Steve On Thursday, 9 April 2020, 17:01:04 BST, Alessandro Muntoni <[email protected]> wrote: Closed #29. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#29 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHCWWOW6M7NOK52BDBEOIE3RLYRMVANCNFSM4C25BYZQ>.

[alemuntoni]

Hi @mickletown, that's really strange.
In the release I linked, if something goes wrong at least an error message should appear.
Did you try the 2020.04 installer?

[mickletown]

Hi Allesandro,I tried both the  2020.04 windows zip and exe files. The exe file could not be processed  as malware messages arose from both Windows and Avast. The zip file opened up, and I was instructed to install the vbasic file, after which a restart, and then on trying to open the meshlab file, then two box flashes on screen and nothing more that I could either see or find. Win 10 home,Intel Graphicsi5 2310 processwor8gb ram Steve  On Friday, 10 April 2020, 11:38:59 BST, Alessandro Muntoni <[email protected]> wrote: Hi @mickletown, that's really strange. In the release I linked, if something goes wrong at least an error message should appear. Did you try the 2020.04 installer? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[alemuntoni]

@mickletown Could you please try to rename the file opengl32sw.dll to opengl32.dll in the meshlab folder, and then restart meshlab?

[mickletown]

Tried with same result - no start-up Steve On Friday, 10 April 2020, 16:36:26 BST, Alessandro Muntoni <[email protected]> wrote: @mickletown Could you please try to rename the file opengl32sw.dll to opengl32.dll in the meshlab folder, and then restart meshlab? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[mickletown]

I have just tried the prog out on my alternate PC - 7gb core2 duo, win10 pro with radeon graphics, and it has loaded up OK.I now need to try some of my scans to see what I can do.It appears to me that the intel integrated graphics are the cause of the problem in this version, even though they are rather old in my main desktop. What is strange though is that older versions of meshlab DO run on intel graphic solutions. Steve On Friday, 10 April 2020, 18:14:31 BST, [email protected] <[email protected]> wrote: Tried with same result - no start-up Steve On Friday, 10 April 2020, 16:36:26 BST, Alessandro Muntoni <[email protected]> wrote: @mickletown Could you please try to rename the file opengl32sw.dll to opengl32.dll in the meshlab folder, and then restart meshlab? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.