UV/Image editor paint image crash #31826

New Issue

José Ricarte · 2012-06-14T10:00:59+02:00

José Ricarte commented

2012-06-14 10:00:59 +02:00

%%%2.63.11 r47813
windows/32

UV/Image editor, new image, ok, enable image painting mode.... crash%%%

%%%2.63.11 r47813 windows/32 UV/Image editor, new image, ok, enable image painting mode.... crash%%%

José Ricarte commented

2012-06-14 10:00:59 +02:00

Changed status to: 'Open'

Anthony Edlin commented

2012-06-14 21:23:41 +02:00

%%%Seems to work fine on:

32-bit Kubuntu 12.04
Intel Core2 Quad Q6600@ 2.40GHz
NVidia 8800 GT - Driver version 295.40
Blender 2.63 r47894

Will need more info to find the problem I think.

You can open blender and goto help->system info, then go into blenders text editor and save the system-info.txt file and attach here.

What would really pinpoint the crash better would be a backtrace on the crash from a debug build of blender.%%%

%%%Seems to work fine on: 32-bit Kubuntu 12.04 Intel Core2 Quad Q6600@ 2.40GHz NVidia 8800 GT - Driver version 295.40 Blender 2.63 r47894 Will need more info to find the problem I think. You can open blender and goto help->system info, then go into blenders text editor and save the system-info.txt file and attach here. What would really pinpoint the crash better would be a backtrace on the crash from a debug build of blender.%%%

José Ricarte commented

2012-06-15 09:59:14 +02:00

%%%ok, here goes, is an old computer used in render farm%%%

Anthony Edlin commented

2012-06-17 20:17:21 +02:00

%%%Thanks for getting the system-info.txt file.

I'm not a windows user so I'm not the best to look at it but I can't see anything with the system-info.txt that stands out as being wrong.

In order to narrow down the problem it may help to know if there is a version or revision of blender that works for you, also some more information on where this crashing build is from. Is this a build you've built yourself, is it a build from buildbot or graphicall? Can you try other builds or other computers and see if they work? If you're building your own build, then doing a debug build and then getting a backtrace from it when it crashes maybe would pinpoint the problem. I know that's alot of questions and alot of work but the first thing we need to do is reproduce the problem.

Crashing on just enabling image painting is a pretty easy and big crash. I would think alot of people would be reporting it if it effected them, so it seems more likely that it's more related to your individual system or build, and maybe doing a reinstall/rebuild would clear out the problem.

Thanks for your time on this.%%%

%%%Thanks for getting the system-info.txt file. I'm not a windows user so I'm not the best to look at it but I can't see anything with the system-info.txt that stands out as being wrong. In order to narrow down the problem it may help to know if there is a version or revision of blender that works for you, also some more information on where this crashing build is from. Is this a build you've built yourself, is it a build from buildbot or graphicall? Can you try other builds or other computers and see if they work? If you're building your own build, then doing a debug build and then getting a backtrace from it when it crashes maybe would pinpoint the problem. I know that's alot of questions and alot of work but the first thing we need to do is reproduce the problem. Crashing on just enabling image painting is a pretty easy and big crash. I would think alot of people would be reporting it if it effected them, so it seems more likely that it's more related to your individual system or build, and maybe doing a reinstall/rebuild would clear out the problem. Thanks for your time on this.%%%

Tobias Oelgarte commented

2012-06-18 12:46:24 +02:00

%%%I can repeat the issue with any kind of newly created image on r48019 and also on one week old versions on (Ubuntu 10.10, 32 bit). As soon i press the button to enter the paint mode i get a segmentation fault:

Program received signal SIGSEGV, Segmentation fault.
0x095944bd in paint_get_active_from_context (C=0xca0f4c0)

  at /media/Trekstor_01/temp/blender-build/blender-svn/blender/source/blender/blenkernel/intern/paint.c:99

99 if (obact->mode == OB_MODE_EDIT) {

Steps to reproduce:

Open default file
Changing one window to UV/Image editor
Create a new image (settings doesn't matter)
Press the paint button

As soon i move the mouse now over the image i get this segfault.

%%%

%%%I can repeat the issue with any kind of newly created image on r48019 and also on one week old versions on (Ubuntu 10.10, 32 bit). As soon i press the button to enter the paint mode i get a segmentation fault: Program received signal SIGSEGV, Segmentation fault. 0x095944bd in paint_get_active_from_context (C=0xca0f4c0) ``` at /media/Trekstor_01/temp/blender-build/blender-svn/blender/source/blender/blenkernel/intern/paint.c:99 ``` 99 if (obact->mode == OB_MODE_EDIT) { Steps to reproduce: 1. Open default file 2. Changing one window to UV/Image editor 3. Create a new image (settings doesn't matter) 4. Press the paint button As soon i move the mouse now over the image i get this segfault. %%%

Sergey Sharybin commented

2012-06-18 16:09:20 +02:00

%%%Fixed in svn rev48039. Thanks for the report, closing.%%%

Sergey Sharybin commented

2012-06-18 16:09:20 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2012-06-18 16:09:20 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

UV/Image editor paint image crash #31826